pgsql: doc PG 17 relnotes: move partition access method item

doc PG 17 relnotes: move partition access method item Also clarify wording. Reported-by: Álvaro Herrera Discussion: https://postgr.es/m/202409111750.xtcbl7ppdoyn@alvherre.pgsql Backpatch-through: 17 only Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/4e7

pgsql: doc PG 17 relnotes: add dynamic shared memory registry item

doc PG 17 relnotes: add dynamic shared memory registry item Reported-by: Nathan Bossart Discussion: https://postgr.es/m/Ztcuwbs0FGCPOEu9@nathan Backpatch-through: 17 only Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/26cea9fb8232d0ec8b4d637e2aa9558c9c6fb

pgsql: Allow _h_indexbuild() to be interrupted.

Allow _h_indexbuild() to be interrupted. When we are building a hash index that is large enough to need pre-sorting (larger than either maintenance_work_mem or NBuffers), the initial sorting phase is interruptible, but the insertion phase wasn't. Add the missing CHECK_FOR_INTERRUPTS(). Per bug #

pgsql: Allow _h_indexbuild() to be interrupted.

Allow _h_indexbuild() to be interrupted. When we are building a hash index that is large enough to need pre-sorting (larger than either maintenance_work_mem or NBuffers), the initial sorting phase is interruptible, but the insertion phase wasn't. Add the missing CHECK_FOR_INTERRUPTS(). Per bug #

pgsql: Allow _h_indexbuild() to be interrupted.

Allow _h_indexbuild() to be interrupted. When we are building a hash index that is large enough to need pre-sorting (larger than either maintenance_work_mem or NBuffers), the initial sorting phase is interruptible, but the insertion phase wasn't. Add the missing CHECK_FOR_INTERRUPTS(). Per bug #

pgsql: Allow _h_indexbuild() to be interrupted.

Allow _h_indexbuild() to be interrupted. When we are building a hash index that is large enough to need pre-sorting (larger than either maintenance_work_mem or NBuffers), the initial sorting phase is interruptible, but the insertion phase wasn't. Add the missing CHECK_FOR_INTERRUPTS(). Per bug #

pgsql: Allow _h_indexbuild() to be interrupted.

Allow _h_indexbuild() to be interrupted. When we are building a hash index that is large enough to need pre-sorting (larger than either maintenance_work_mem or NBuffers), the initial sorting phase is interruptible, but the insertion phase wasn't. Add the missing CHECK_FOR_INTERRUPTS(). Per bug #

pgsql: Allow _h_indexbuild() to be interrupted.

Allow _h_indexbuild() to be interrupted. When we are building a hash index that is large enough to need pre-sorting (larger than either maintenance_work_mem or NBuffers), the initial sorting phase is interruptible, but the insertion phase wasn't. Add the missing CHECK_FOR_INTERRUPTS(). Per bug #

pgsql: Allow _h_indexbuild() to be interrupted.

Allow _h_indexbuild() to be interrupted. When we are building a hash index that is large enough to need pre-sorting (larger than either maintenance_work_mem or NBuffers), the initial sorting phase is interruptible, but the insertion phase wasn't. Add the missing CHECK_FOR_INTERRUPTS(). Per bug #

pgsql: Add commit 2b03cfeea4 to .git-blame-ignore-revs.

Add commit 2b03cfeea4 to .git-blame-ignore-revs. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/9a23967063b1b36c620a753f72c7cdb56dc0a4c4 Modified Files -- .git-blame-ignore-revs | 3 +++ 1 file changed, 3 insertions(+)

pgsql: doc PG 17 relnotes: replace commit hashes with section marks

doc PG 17 relnotes: replace commit hashes with section marks Backpatch-through: 17 only Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/b9a65a678b68dfab47bff3c9524fc72040a26195 Modified Files -- doc/src/sgml/release-17.sgml | 860 +++

pgsql: Fix contrib/pageinspect's test for sequences.

Fix contrib/pageinspect's test for sequences. I managed to break this test in two different ways in commit 05036a3155. First, the output of the new call to tuple_data_split() on the test sequence is dependent on endianness. This is fixed by setting a special start value for the test sequence tha

pgsql: Fix contrib/pageinspect's test for sequences.

Fix contrib/pageinspect's test for sequences. I managed to break this test in two different ways in commit 05036a3155. First, the output of the new call to tuple_data_split() on the test sequence is dependent on endianness. This is fixed by setting a special start value for the test sequence tha

pgsql: Fix contrib/pageinspect's test for sequences.

Fix contrib/pageinspect's test for sequences. I managed to break this test in two different ways in commit 05036a3155. First, the output of the new call to tuple_data_split() on the test sequence is dependent on endianness. This is fixed by setting a special start value for the test sequence tha

pgsql: Fix contrib/pageinspect's test for sequences.

Fix contrib/pageinspect's test for sequences. I managed to break this test in two different ways in commit 05036a3155. First, the output of the new call to tuple_data_split() on the test sequence is dependent on endianness. This is fixed by setting a special start value for the test sequence tha

pgsql: Fix contrib/pageinspect's test for sequences.

Fix contrib/pageinspect's test for sequences. I managed to break this test in two different ways in commit 05036a3155. First, the output of the new call to tuple_data_split() on the test sequence is dependent on endianness. This is fixed by setting a special start value for the test sequence tha

pgsql: Fix contrib/pageinspect's test for sequences.

Fix contrib/pageinspect's test for sequences. I managed to break this test in two different ways in commit 05036a3155. First, the output of the new call to tuple_data_split() on the test sequence is dependent on endianness. This is fixed by setting a special start value for the test sequence tha

pgsql: Fix contrib/pageinspect's test for sequences.

Fix contrib/pageinspect's test for sequences. I managed to break this test in two different ways in commit 05036a3155. First, the output of the new call to tuple_data_split() on the test sequence is dependent on endianness. This is fixed by setting a special start value for the test sequence tha

pgsql: Remove separate locale_is_c arguments

Remove separate locale_is_c arguments Since e9931bfb751, ctype_is_c is part of pg_locale_t. Some functions passed a pg_locale_t and a bool argument separately. This can now be combined into one argument. Since some callers call MatchText() with locale 0, it is a bit confusing whether this is al

pgsql: doc PG 17 relnotes: add links to commits

doc PG 17 relnotes: add links to commits Copied from SGML comments. Discussion: https://postgr.es/m/cacjufxf+9ycdce5vzmzy6zceetjsyfg-kpoht9ujkikjx30...@mail.gmail.com Author: jian he Backpatch-through: 17 only Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitd

pgsql: SQL/JSON: Update example in JSON_QUERY() documentation

SQL/JSON: Update example in JSON_QUERY() documentation Commit e6c45d85dc fixed the behavior of JSON_QUERY() when WITH CONDITIONAL WRAPPER is used, but the documentation example wasn't updated to reflect this change. This commit updates the example to show the correct result. Per off-list report f

pgsql: SQL/JSON: Update example in JSON_QUERY() documentation

SQL/JSON: Update example in JSON_QUERY() documentation Commit 2c27346ed684 fixed the behavior of JSON_QUERY() when WITH CONDITIONAL WRAPPER is used, but the documentation example wasn't updated to reflect this change. This commit updates the example to show the correct result. Per off-list report