diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-08-31 13:53:33 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-08-31 13:53:50 -0400 |
commit | 904ce45bfa8862d4ae04065c8033182ad812b009 (patch) | |
tree | dbf4a5aaa6ad2ee8dc25a7c5f1d26ea5625d43d4 /src/backend/executor/nodeFunctionscan.c | |
parent | c8213aa949626deb19f098332eded3586624ff59 (diff) | |
download | postgresql-904ce45bfa8862d4ae04065c8033182ad812b009.tar.gz postgresql-904ce45bfa8862d4ae04065c8033182ad812b009.zip |
Cache the results of format_type() queries in pg_dump.
There's long been a "TODO: there might be some value in caching
the results" annotation on pg_dump's getFormattedTypeName function;
but we hadn't gotten around to checking what it was costing us to
repetitively look up type names. It turns out that when dumping the
current regression database, about 10% of the total number of queries
issued are duplicative format_type() queries. However, Hubert Depesz
Lubaczewski reported a not-unusual case where these account for over
half of the queries issued by pg_dump. Individually these queries
aren't expensive, but when network lag is a factor, they add up to a
problem. We can very easily add some caching to getFormattedTypeName
to solve it.
Since this is such a simple fix and can have a visible performance
benefit, back-patch to all supported branches.
Discussion: https://postgr.es/m/20210826084430.GA26282@depesz.com
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions