Remove plpgsql's special-case code paths for SET/RESET.
In the wake of 84f5c2908, it's no longer necessary for plpgsql to
handle SET/RESET specially. The point of that was just to avoid
taking a new transaction snapshot prematurely, which the regular code
path through _SPI_execute_plan() now does
Update PG 14 relnotes for vacuum_cost_page_miss
Reported-by: Peter Geoghegan
Discussion:
https://postgr.es/m/cah2-wzmgsndx9wvoxrzxukecy2mzlo9dmo4+go0rznw0vbd...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/8dcae7f0a3d6aba1afad1599ab18d259c417b4ee
doc: PG 14 relnotes, adjust pg_{read|write}_all_data entry
Reported-by: Stephen Frost
Discussion: https://postgr.es/m/[email protected]
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/7ce7d07e1c5fb33ee56bda235ae3d53f162f3bc0
Modified File
Fix access to no-longer-open relcache entry in logical-rep worker.
If we redirected a replicated tuple operation into a partition child
table, and then tried to fire AFTER triggers for that event, the
relation cache entry for the child table was already closed. This has
no visible ill effects as
Fix access to no-longer-open relcache entry in logical-rep worker.
If we redirected a replicated tuple operation into a partition child
table, and then tried to fire AFTER triggers for that event, the
relation cache entry for the child table was already closed. This has
no visible ill effects as
doc: word-wrap and indent PG 14 relnotes
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/8f73ed6b659464274eb9cc8358588b569960d0be
Modified Files
--
doc/src/sgml/release-14.sgml | 3649 --
1 file changed, 2094 inser
