aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-12-30 19:40:37 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2021-12-30 19:40:53 -0500
commit5e65df64d631257ce60016bec0aca43f042b1d33 (patch)
tree2b4be2c0ce8ba0c7523cee5dd7796ba4ed4f0122 /src/backend/executor
parentc9105dd3660f4a801e6f87a1ed68189bd30576bf (diff)
downloadpostgresql-5e65df64d631257ce60016bec0aca43f042b1d33.tar.gz
postgresql-5e65df64d631257ce60016bec0aca43f042b1d33.zip
pg_dump: make dumpPublication et al. less unlike sibling functions.
dumpPublication, dumpPublicationNamespace, dumpPublicationTable, and dumpSubscription failed to check dataOnly. This is just a latent bug, because pg_backup_archiver.c would filter out the ArchiveEntry later; but they're wasting cycles in data-only dumps, and the omission might become a live bug someday. In any case, it's not good to have some dumpFoo functions do this and some not. On the same reasoning, make dumpPublicationNamespace follow the same pattern as every other dumpFoo function for checking the DUMP_COMPONENT_DEFINITION flag. (Since 5209c0ba0, we wouldn't even get here if that flag isn't set, so checking it is just pro forma right now. But it might not be so forever.) Since this is just cosmetic and/or future-proofing, no need for back-patch.
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions