pgsql: Stabilize test case added by commit f61db909d.

Stabilize test case added by commit f61db909d. Buildfarm members ayu and tern have sometimes shown a different plan than expected for this query. I'd been unable to reproduce that before today, but I finally realized what is happening. If there is a concurrent open transaction (probably an autova

pgsql: Revert "Add test case for obsoleting slot with active walsender"

Revert "Add test case for obsoleting slot with active walsender" This reverts commit 09126984a263; the test case added there failed once in circumstances that remain mysterious. It seems better to remove the test for now so that 14beta2 doesn't have random failures built in. Branch -- master

pgsql: Remove overzealous VACUUM failsafe assertions.

Remove overzealous VACUUM failsafe assertions. The failsafe can trigger when index processing is already disabled. This can happen when VACUUM's INDEX_CLEANUP parameter is "off" and the failsafe happens to trigger. Remove assertions that assume that index processing is directly tied to the failsa

pgsql: doc: add mention of +4GB windows file handling in PG14 relnotes

doc: add mention of +4GB windows file handling in PG14 relnotes Reported-by: Masahiko Sawada Discussion: https://postgr.es/m/cad21aocthyouogv-xt1qnjjvpbgmerli0ajncbytvr66nq7...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/90855908b751d40f67352fa

pgsql: doc: adjust PG 14 relnotes to be current

doc: adjust PG 14 relnotes to be current Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/69a58bfe4ab05567a8fab8bdce7f3095ed06b99c Modified Files -- doc/src/sgml/release-14.sgml | 16 +--- 1 file changed, 13 insertions(+), 3 deletions(-)