pgsql: Repair unstable regression test.

Repair unstable regression test. Commit 0c882e52a tried to force table atest12 to have more-accurate- than-default statistics; but transiently setting default_statistics_target isn't enough for that, because autovacuum could come along and overwrite the stats later. This evidently explains some i

pgsql: Repair unstable regression test.

Repair unstable regression test. Commit 0c882e52a tried to force table atest12 to have more-accurate- than-default statistics; but transiently setting default_statistics_target isn't enough for that, because autovacuum could come along and overwrite the stats later. This evidently explains some i

pgsql: Fix HashAgg regression from choosing too many initial buckets.

Fix HashAgg regression from choosing too many initial buckets. Diagnosis by Andres. Reported-by: Pavel Stehule Discussion: https://postgr.es/m/CAFj8pRDLVakD5Aagt3yZeEQeTeEWaS3YE5h8XC3Q3qJ6TYkc2Q%40mail.gmail.com Backpatch-through: 13 Branch -- REL_13_STABLE Details --- https://git.post

pgsql: Fix HashAgg regression from choosing too many initial buckets.

Fix HashAgg regression from choosing too many initial buckets. Diagnosis by Andres. Reported-by: Pavel Stehule Discussion: https://postgr.es/m/CAFj8pRDLVakD5Aagt3yZeEQeTeEWaS3YE5h8XC3Q3qJ6TYkc2Q%40mail.gmail.com Backpatch-through: 13 Branch -- master Details --- https://git.postgresql.

pgsql: Avoid need for valgrind suppressions for pg_atomic_init_u64 on s

Avoid need for valgrind suppressions for pg_atomic_init_u64 on some platforms. Previously we used pg_atomic_write_64_impl inside pg_atomic_init_u64. That works correctly, but on platforms without 64bit single copy atomicity it could trigger spurious valgrind errors about uninitialized memory, beca

pgsql: Avoid need for valgrind suppressions for pg_atomic_init_u64 on s

Avoid need for valgrind suppressions for pg_atomic_init_u64 on some platforms. Previously we used pg_atomic_write_64_impl inside pg_atomic_init_u64. That works correctly, but on platforms without 64bit single copy atomicity it could trigger spurious valgrind errors about uninitialized memory, beca

pgsql: Avoid need for valgrind suppressions for pg_atomic_init_u64 on s

Avoid need for valgrind suppressions for pg_atomic_init_u64 on some platforms. Previously we used pg_atomic_write_64_impl inside pg_atomic_init_u64. That works correctly, but on platforms without 64bit single copy atomicity it could trigger spurious valgrind errors about uninitialized memory, beca

pgsql: Avoid need for valgrind suppressions for pg_atomic_init_u64 on s

Avoid need for valgrind suppressions for pg_atomic_init_u64 on some platforms. Previously we used pg_atomic_write_64_impl inside pg_atomic_init_u64. That works correctly, but on platforms without 64bit single copy atomicity it could trigger spurious valgrind errors about uninitialized memory, beca

pgsql: Avoid need for valgrind suppressions for pg_atomic_init_u64 on s

Avoid need for valgrind suppressions for pg_atomic_init_u64 on some platforms. Previously we used pg_atomic_write_64_impl inside pg_atomic_init_u64. That works correctly, but on platforms without 64bit single copy atomicity it could trigger spurious valgrind errors about uninitialized memory, beca

pgsql: Avoid need for valgrind suppressions for pg_atomic_init_u64 on s

Avoid need for valgrind suppressions for pg_atomic_init_u64 on some platforms. Previously we used pg_atomic_write_64_impl inside pg_atomic_init_u64. That works correctly, but on platforms without 64bit single copy atomicity it could trigger spurious valgrind errors about uninitialized memory, beca

pgsql: Avoid need for valgrind suppressions for pg_atomic_init_u64 on s

Avoid need for valgrind suppressions for pg_atomic_init_u64 on some platforms. Previously we used pg_atomic_write_64_impl inside pg_atomic_init_u64. That works correctly, but on platforms without 64bit single copy atomicity it could trigger spurious valgrind errors about uninitialized memory, beca

pgsql: Update documentation for snowball update

Update documentation for snowball update Discussion: https://www.postgresql.org/message-id/flat/a8eeabd6-2be1-43fe-401e-a97594c38478%402ndquadrant.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/c2e71cb355a43d3ea0eaa6433d07f3681f934d54 Modified Files -