Request For Feature: pg_dump
Request For Feature: pg_dump
От:
Ron Johnson <ronljohnsonjr@gmail.com>
Дата:
In --format=directory mode, remove .dat files with zero data records, and mark that table's toc.dat entry that it's an empty table.
Justification: lots of empty tables means lots of teeny-tiny files in the DB's dump directory. That unnecessarily bloats the fs, and makes "du -c" really really slow.
But why are there sooo many empty tables? You shouldn't have so many empty tables!
Yeah, well, software (especially 3rd-party software that must be generic to satisfy the varying needs of a large and varied customer base) can't always be perfectly tuned to the precise and immediate needs of a particular site. Partitioning makes that much much worse.
We've survived this long without it, but pgbackrest has a similar feature (though implemented differently from how pg_dump would do it), and it's really handy.
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
Any known bugs with respect to data corruption in pg12/pg 14
От:
Ramakrishna Reddy Nandyala <rkreddy.n@gmail.com>
Дата:
Hi Gurus
We are facing a peculiar issue with respect to pg 12 and pg14 on RHEL8u10,post os patch objects are getting corrupted. The details are unknown until we access the object's.
System Stack:
Db: pg12.22,pg14.19
Os : Rhel 8u10
THALES CTM FOR encryption solution
Stirage : Pure storage and VSAN DISK
We are not seeing any errors reported with respect to the corruption,unless until we select The problematic object that to the problematic block only
Below corruption scenarios we observed
1) if the corruption happen on standby node no impact to the production
2) if corruption happen on production we could see same object we are unable to select from standby node,means corruption is transfer to standby node
3) if the corruption happen on block 0 it is not allowing to perform any DML activity,if it is on other blocks it is allowing to insert/update/delete in other good blocks,if system touches the problematic block only it is failing
Need your guide lines how to identify what is going wrong,and where is going wrong?
Is there any known bugs in these version with the given stack pg12/14 with RHEL8u10
Is there any way we can stop not to replicate the problematic block to standby node?
What will be the best practice to identify the problematic objects or blocks
We tried amcheck on pg14 it is not giving any results
Your expertise advise will be help us on coming out of the critical issue
Re: Any known bugs with respect to data corruption in pg12/pg 14
От:
Alicja Kucharczyk <zaledwie10minut@gmail.com>
Дата:
Hi, for known PostgreSQL corruption-related fixes you can check this filtered list: https://why-upgrade.depesz.com/show?from=12&to=18.4&keywords=corruption.
To identify problematic objects/blocks, I would first try a classic read-through test with pg_dump dbname > /dev/null 2> errors.log, but be careful because this can be heavy on a busy production system.
To identify problematic objects/blocks, I would first try a classic read-through test with pg_dump dbname > /dev/null 2> errors.log, but be careful because this can be heavy on a busy production system.
Re: Any known bugs with respect to data corruption in pg12/pg 14
От:
Alija Rahmanovic <rmc.aly17@gmail.com>
Дата:
👍
V sre., 3. jun. 2026 14:33 je oseba Alicja Kucharczyk <zaledwie10minut@gmail.com> napisala:
Hi, for known PostgreSQL corruption-related fixes you can check this filtered list: https://why-upgrade.depesz.com/show?from=12&to=18.4&keywords=corruption.
To identify problematic objects/blocks, I would first try a classic read-through test with pg_dump dbname > /dev/null 2> errors.log, but be careful because this can be heavy on a busy production system.