In pg_dump, don't dump a stats object unless dumping underlying table.
Tom Lane <tgl@sss.pgh.pa.us>
In pg_dump, don't dump a stats object unless dumping underlying table. If the underlying table isn't being dumped, it's useless to dump an extended statistics object; it'll just cause errors at restore. We have always applied similar policies to, say, indexes. (When and if we get cross-table stats objects, it might be profitable to think a little harder about what to do with them. But for now there seems no point in considering a stats object as anything but an appendage of its table.) Rian McGuire and Tom Lane, per report from Rian McGuire. Back-patch to supported branches. Discussion: https://postgr.es/m/7075d3aa-3f05-44a5-b68f-47dc6a8a0550@buildkite.com
Files
| Path | Change | +/− |
|---|---|---|
| src/bin/pg_dump/pg_dump.c | modified | +27 −3 |
| src/bin/pg_dump/pg_dump.h | modified | +2 −1 |
| src/bin/pg_dump/t/002_pg_dump.pl | modified | +3 −3 |
Discussion
- [PATCH] pg_dump: Do not dump statistics for excluded tables 2 messages · 2023-12-27