Using the Expand and Contract Pattern in PostgreSQL
When you change the structure of a PostgreSQL database while application instances are running, the expand and contract pattern lets old and new application versions work at the…
Read articleArticles
Page 4 of 4.
What Happens During a PostgreSQL CREATE INDEX CONCURRENTLY Build
When you add an index to a PostgreSQL table serving production traffic, PostgreSQL blocks writes to the table until a regular CREATE INDEX finishes. CREATE INDEX CONCURRENTLY lets…
Read articleWhat VACUUM and ANALYZE Do in PostgreSQL
PostgreSQL uses multiversion concurrency control, or MVCC, to let transactions read consistent data while other transactions change it. When a transaction updates or deletes a row, PostgreSQL keeps…
Read articleWhen to Use PostgreSQL B-Tree Indexes
For most PostgreSQL queries that look for an exact value, check whether values fall within a span, or return rows in order, start with a B-tree index. A…
Read articleWhen to Use PostgreSQL GIN Indexes
When a PostgreSQL query searches inside an array or JSONB document, or looks for terms in full-text search data, a GIN index can find rows that match the…
Read articleWhen to Use PostgreSQL GiST Indexes
In PostgreSQL, choose a Generalized Search Tree (GiST) index when the rules for a data type’s operators, called its operator class, support the search your query performs. GiST…
Read articleWhy PostgreSQL SERIALIZABLE Transactions Still Need Retries
When PostgreSQL runs concurrent transactions at SERIALIZABLE isolation, it guarantees that the committed transactions produce the same result as if they ran one at a time. To keep…
Read articleWhy Safe PostgreSQL Migrations Require Short Transactions
When a migration runs in one long transaction, PostgreSQL keeps its locks until the transaction ends. The migration also leaves more unfinished changes to roll back, and a…
Read article