pgsql: Update obsolete comment

Update obsolete comment table_tuple_update's update_indexes argument hasn't been a boolean since commit 19d8e2308bc5. Backpatch-through: 16 Branch -- REL_18_STABLE Details --- https://git.postgresql.org/pg/commitdiff/649bd26a4021c2a00999ecea2296c459a21d84dc Modified Files -

pgsql: Update obsolete comment

Update obsolete comment table_tuple_update's update_indexes argument hasn't been a boolean since commit 19d8e2308bc5. Backpatch-through: 16 Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/f3ac3cbb14f01358a30624aafc3771f12a62e9ff Modified Files -

pgsql: Update obsolete comment

Update obsolete comment table_tuple_update's update_indexes argument hasn't been a boolean since commit 19d8e2308bc5. Backpatch-through: 16 Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/f4ec7154ce8d3e3a572baea682c1f58890a72589 Modified Files -

pgsql: Update obsolete comment

Update obsolete comment table_tuple_update's update_indexes argument hasn't been a boolean since commit 19d8e2308bc5. Backpatch-through: 16 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3894f08abe490d31518d038b0a8eaa46ce971b03 Modified Files -- src/i

pgsql: Use standard die() handler for SIGTERM in bgworkers

Use standard die() handler for SIGTERM in bgworkers The previous default bgworker_die() signal would exit with elog(FATAL) directly from the signal handler. That could cause deadlocks or crashes if the signal handler runs while we're e.g holding a spinlock or in the middle of a memory allocation.

pgsql: Simplify creation of built-in functions with default arguments.

Simplify creation of built-in functions with default arguments. Up to now, to create such a function, one had to make a pg_proc.dat entry and then overwrite it with a CREATE OR REPLACE command in system_functions.sql. That's error-prone (cf. bug #19409) and results in leaving dead rows in the ini

pgsql: Fix the volatility setting of json{b}_strip_nulls

Fix the volatility setting of json{b}_strip_nulls Commit 4603903d294 unfortunately reset the volatility of these functions to STABLE whereas they had previously been set to IMMUTABLE. We can't force a catalog update in the stable release, although a pg_update would probably do the trick. A simpler

pgsql: Sanitize some WAL-logging buffer handling in GIN and GiST code

Sanitize some WAL-logging buffer handling in GIN and GiST code As transam's README documents, the general order of actions recommended when WAL-logging a buffer is to unlock and unpin buffers after leaving a critical section. This pattern was not being followed by some code paths of GIN and GiST,