pgsql: Use InvalidBucket instead of -1 where appropriate

Use InvalidBucket instead of -1 where appropriate Reported-by: Ranier Vilela Discussion: https://www.postgresql.org/message-id/flat/CAEudQAp%3DZwKjrP4L%2BCzqV7SmWiaQidPPRqj4tqdjDG4KBx5yrg%40mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/6bd3ec62d9d

pgsql: doc: PG 14 relnotes, mention CONCURRENTLY improvements

doc: PG 14 relnotes, mention CONCURRENTLY improvements Add items for vacuum not having to wait for CONCURRENTLY, and CONCURRENTLY not having to wait for other CONCURRENTLY operations. Reported-by: Simon Riggs Discussion: https://postgr.es/m/canbhv-emm4nf7ys-yae_ky25dxt_3eioxke2+yw44jgy+4j...@m

pgsql: Don't try to print data type names in slot_store_error_callback(

Don't try to print data type names in slot_store_error_callback(). The existing code tried to do syscache lookups in an already-failed transaction, which is problematic to say the least. After some consideration of alternatives, the best fix seems to be to just drop type names from the error mess

pgsql: Don't try to print data type names in slot_store_error_callback(

Don't try to print data type names in slot_store_error_callback(). The existing code tried to do syscache lookups in an already-failed transaction, which is problematic to say the least. After some consideration of alternatives, the best fix seems to be to just drop type names from the error mess

pgsql: Don't try to print data type names in slot_store_error_callback(

Don't try to print data type names in slot_store_error_callback(). The existing code tried to do syscache lookups in an already-failed transaction, which is problematic to say the least. After some consideration of alternatives, the best fix seems to be to just drop type names from the error mess

pgsql: Don't try to print data type names in slot_store_error_callback(

Don't try to print data type names in slot_store_error_callback(). The existing code tried to do syscache lookups in an already-failed transaction, which is problematic to say the least. After some consideration of alternatives, the best fix seems to be to just drop type names from the error mess

pgsql: Don't try to print data type names in slot_store_error_callback(

Don't try to print data type names in slot_store_error_callback(). The existing code tried to do syscache lookups in an already-failed transaction, which is problematic to say the least. After some consideration of alternatives, the best fix seems to be to just drop type names from the error mess

pgsql: Don't try to print data type names in slot_store_error_callback(

Don't try to print data type names in slot_store_error_callback(). The existing code tried to do syscache lookups in an already-failed transaction, which is problematic to say the least. After some consideration of alternatives, the best fix seems to be to just drop type names from the error mess

pgsql: docs: clarify new aggressive vacuum mode for multi-xacts

docs: clarify new aggressive vacuum mode for multi-xacts Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 14 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/c552e17

pgsql: docs: clarify new aggressive vacuum mode for multi-xacts

docs: clarify new aggressive vacuum mode for multi-xacts Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 14 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/

pgsql: doc: adjust "cities" example to be consistent with other SQL

doc: adjust "cities" example to be consistent with other SQL Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.6 Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdif

pgsql: doc: adjust "cities" example to be consistent with other SQL

doc: adjust "cities" example to be consistent with other SQL Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.6 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdif

pgsql: doc: adjust "cities" example to be consistent with other SQL

doc: adjust "cities" example to be consistent with other SQL Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.6 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdif

pgsql: doc: adjust "cities" example to be consistent with other SQL

doc: adjust "cities" example to be consistent with other SQL Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.6 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdif

pgsql: doc: adjust "cities" example to be consistent with other SQL

doc: adjust "cities" example to be consistent with other SQL Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.6 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/d390b

pgsql: doc: adjust "cities" example to be consistent with other SQL

doc: adjust "cities" example to be consistent with other SQL Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.6 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdif

pgsql: doc: adjust "cities" example to be consistent with other SQL

doc: adjust "cities" example to be consistent with other SQL Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.6 Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdif