aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/async.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-12-06 13:14:29 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2021-12-06 13:14:29 -0500
commitbe85727a3df743a1f7e93b41dd7ac2b667e8ae04 (patch)
tree455891fccb1e8f103a0b75aee743ef7289f8aa4c /src/backend/commands/async.c
parent9895961529ef8ff3fc12b39229f9a93e08bca7b7 (diff)
downloadpostgresql-be85727a3df743a1f7e93b41dd7ac2b667e8ae04.tar.gz
postgresql-be85727a3df743a1f7e93b41dd7ac2b667e8ae04.zip
Use PREPARE/EXECUTE for repetitive per-object queries in pg_dump.
For objects such as functions, pg_dump issues the same secondary data-collection query against each object to be dumped. This can't readily be refactored to avoid the repetitive queries, but we can PREPARE these queries to reduce planning costs. This patch applies the idea to functions, aggregates, operators, and data types. While it could be carried further, the remaining sorts of objects aren't likely to appear in typical databases enough times to be worth worrying over. Moreover, doing the PREPARE is likely to be a net loss if there aren't at least some dozens of objects to apply the prepared query to. Discussion: https://postgr.es/m/7d7eb6128f40401d81b3b7a898b6b4de@W2012-02.nidsa.loc
Diffstat (limited to 'src/backend/commands/async.c')
0 files changed, 0 insertions, 0 deletions