[COMMITTERS] pgsql: Add note about diskspace usage of pg_commit_ts

Add note about diskspace usage of pg_commit_ts Author: Thomas Munro Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/abe85ef1d00187a42e7a757ea0413bc4965a4525 Modified Files -- doc/src/sgml/maintenance.sgml | 30 +- 1 file chang

[COMMITTERS] pgsql: Add note about diskspace usage of pg_commit_ts

Add note about diskspace usage of pg_commit_ts Author: Thomas Munro Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/28915c7db4da4eaffb8eb0dc5c04c87dcf345eb6 Modified Files -- doc/src/sgml/maintenance.sgml | 30 +- 1 fil

[COMMITTERS] pgsql: Fix assorted carelessness about Datum vs. int64 vs. uint64

Fix assorted carelessness about Datum vs. int64 vs. uint64 Bugs introduced by commit 81c5e46c490e2426db243eada186995da5bb0ba7 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/7b69b6ceb8047979ddf82af12ec1de143da62263 Modified Files -- src/backend/utils/ad

[COMMITTERS] pgsql: Try to repair poorly-considered code in previous commit.

Try to repair poorly-considered code in previous commit. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/0d9506d125beef18247a5e38a219d3b23e2d312e Modified Files -- src/backend/utils/adt/jsonb_op.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

Re: [COMMITTERS] pgsql: Introduce 64-bit hash functions with a 64-bit seed.

Robert Haas writes: > Introduce 64-bit hash functions with a 64-bit seed. Buildfarm is not terribly impressed with this. regards, tom lane -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postg

[COMMITTERS] pgsql: Introduce 64-bit hash functions with a 64-bit seed.

Introduce 64-bit hash functions with a 64-bit seed. This will be useful for hash partitioning, which needs a way to seed the hash functions to avoid problems such as a hash index on a hash partitioned table clumping all values into a small portion of the bucket space; it's also useful for anything

[COMMITTERS] pgsql: Avoid memory leaks when a GatherMerge node is rescanned.

Avoid memory leaks when a GatherMerge node is rescanned. Rescanning a GatherMerge led to leaking some memory in the executor's query-lifespan context, because most of the node's working data structures were simply abandoned and rebuilt from scratch. In practice, this might never amount to much, g

[COMMITTERS] pgsql: Avoid memory leaks when a GatherMerge node is rescanned.

Avoid memory leaks when a GatherMerge node is rescanned. Rescanning a GatherMerge led to leaking some memory in the executor's query-lifespan context, because most of the node's working data structures were simply abandoned and rebuilt from scratch. In practice, this might never amount to much, g

[COMMITTERS] pgsql: Improve low-level backup documentation.

Improve low-level backup documentation. Our documentation hasn't really caught up with the fact that non-exclusive backups can now be taken using pg_start_backup and pg_stop_backup even on standbys. Update. David Steele, reviewed by Robert Haas and Michael Paquier Discussion: http://postgr.es/

[COMMITTERS] pgsql: Expand partitioned tables in PartDesc order.

Expand partitioned tables in PartDesc order. Previously, we expanded the inheritance hierarchy in the order in which find_all_inheritors had locked the tables, but that turns out to block quite a bit of useful optimization. For example, a partition-wise join can't count on two tables with matchin

[COMMITTERS] pgsql: Clean up shm_mq cleanup.

Clean up shm_mq cleanup. The logic around shm_mq_detach was a few bricks shy of a load, because (contrary to the comments for shm_mq_attach) all it did was update the shared shm_mq state. That left us leaking a bit of process-local memory, but much worse, the on_dsm_detach callback for shm_mq_det

[COMMITTERS] pgsql: Clean up shm_mq cleanup.

Clean up shm_mq cleanup. The logic around shm_mq_detach was a few bricks shy of a load, because (contrary to the comments for shm_mq_attach) all it did was update the shared shm_mq state. That left us leaking a bit of process-local memory, but much worse, the on_dsm_detach callback for shm_mq_det

[COMMITTERS] pgsql: Improve code coverage of select_parallel test.

Improve code coverage of select_parallel test. Make sure that rescans of parallel indexscans are tested. Per code coverage report. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4b1dd62a257a469f92fef4f4cce37beab6c0b98b Modified Files -- src/test/regres

[COMMITTERS] pgsql: Improve code coverage of select_parallel test.

Improve code coverage of select_parallel test. Make sure that rescans of parallel indexscans are tested. Per code coverage report. Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/4c7af96365d6a50c4f807a97dd37ac3e9c7459cf Modified Files -- src/test