pgsql: doc PG 17 relnotes: adjust "builtin" collation provider

doc PG 17 relnotes: adjust "builtin" collation provider Reported-by: Daniel Verite Discussion: https://postgr.es/m/13447ff6-15fd-4137-8339-f4fddda7e...@manitou-mail.org Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/acecd6746cdc2df5ba8

pgsql: doc PG 17 relnotes: update to current

doc PG 17 relnotes: update to current Reported-by: jian he Discussion: https://postgr.es/m/cacjufxe7fbwckfexdw86vtia2bv+locfnr-apf1cp2fjxeb...@mail.gmail.com Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/15b4d463083b1afd515f2322de7f1b

pgsql: Account for optimized MinMax aggregates during SS_finalize_plan.

Account for optimized MinMax aggregates during SS_finalize_plan. We are capable of optimizing MIN() and MAX() aggregates on indexed columns into subqueries that exploit the index, rather than the normal thing of scanning the whole table. When we do this, we replace the Aggref node(s) with Params

pgsql: Account for optimized MinMax aggregates during SS_finalize_plan.

Account for optimized MinMax aggregates during SS_finalize_plan. We are capable of optimizing MIN() and MAX() aggregates on indexed columns into subqueries that exploit the index, rather than the normal thing of scanning the whole table. When we do this, we replace the Aggref node(s) with Params

pgsql: Account for optimized MinMax aggregates during SS_finalize_plan.

Account for optimized MinMax aggregates during SS_finalize_plan. We are capable of optimizing MIN() and MAX() aggregates on indexed columns into subqueries that exploit the index, rather than the normal thing of scanning the whole table. When we do this, we replace the Aggref node(s) with Params

pgsql: Account for optimized MinMax aggregates during SS_finalize_plan.

Account for optimized MinMax aggregates during SS_finalize_plan. We are capable of optimizing MIN() and MAX() aggregates on indexed columns into subqueries that exploit the index, rather than the normal thing of scanning the whole table. When we do this, we replace the Aggref node(s) with Params

pgsql: Account for optimized MinMax aggregates during SS_finalize_plan.

Account for optimized MinMax aggregates during SS_finalize_plan. We are capable of optimizing MIN() and MAX() aggregates on indexed columns into subqueries that exploit the index, rather than the normal thing of scanning the whole table. When we do this, we replace the Aggref node(s) with Params

pgsql: Add test case showing that commit d0d44049d fixed a live bug.

Add test case showing that commit d0d44049d fixed a live bug. When I committed d0d44049d (Account for optimized MinMax aggregates during SS_finalize_plan), I didn't have a test case showing that it was fixing any reachable bug. Here is one, based on bug #18465 from Hal Takahara. Without the fix,

pgsql: doc PG 17 relnotes: add incremental JSON parser item

doc PG 17 relnotes: add incremental JSON parser item Reported-by: Andrew Dunstan Discussion: https://postgr.es/m/e48dbf1e-62c9-4dbb-8b42-bb9ed898a...@dunslane.net Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3f49df98d8b97adc37f408ef3

pgsql: doc PG 17 relnotes: improve JSON casting item

doc PG 17 relnotes: improve JSON casting item Reported-by: jian he Discussion: https://postgr.es/m/cacjufxe0hy19f8oo-wb-+i4bkdamial_auv8qb69_8mwosc...@mail.gmail.com Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/58294448797ead5b9d7ee0

pgsql: doc PG 17 relnotes: adjust vacuum memory item

doc PG 17 relnotes: adjust vacuum memory item Reported-by: David Rowley Discussion: https://postgr.es/m/caaphdvpznr+wrmx5wic9na60fzsbrueffmoecvubbjv483j...@mail.gmail.com Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/b67478b99b7452540