aboutsummaryrefslogtreecommitdiff
path: root/contrib/intarray/_int_gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2023-12-29 10:57:11 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2023-12-29 10:57:11 -0500
commit1e0841426e968f184277e7638227b16fb3cdca7a (patch)
tree0769210a129150ed8bffac015f90c6c600f778e2 /contrib/intarray/_int_gist.c
parent296128a53646126fc33394ca859df5ab000c4798 (diff)
downloadpostgresql-1e0841426e968f184277e7638227b16fb3cdca7a.tar.gz
postgresql-1e0841426e968f184277e7638227b16fb3cdca7a.zip
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
Diffstat (limited to 'contrib/intarray/_int_gist.c')
0 files changed, 0 insertions, 0 deletions