diff options
| author | Peter Geoghegan <pg@bowt.ie> | 2023-03-31 14:02:52 -0700 |
|---|---|---|
| committer | Peter Geoghegan <pg@bowt.ie> | 2023-03-31 14:02:52 -0700 |
| commit | df4f3ab51730a4cdddfead0b264d394ee4925723 (patch) | |
| tree | 95b086f2a6e89b192555dd1bb1408f3225d45ae5 /src/backend/access/gist/gistbuild.c | |
| parent | 6ee30209a6f161d0a267a33f090c70c579c87c00 (diff) | |
| download | postgresql-df4f3ab51730a4cdddfead0b264d394ee4925723.tar.gz | |
Add show_data option to pg_get_wal_block_info.
Allow users to opt out of returning FPI data and block data from
pg_get_wal_block_info as an optimization. Testing has shown that this
can make function execution over twice as fast in some cases.
When pg_get_wal_block_info is called with "show_data := false", it
always returns NULL values for its block_data and block_fpi_data bytea
output parameters. Nothing else changes. In particular, the function
will still return the usual per-block summary of block data/FPI space
overhead. Use of "show_data := false" is therefore feasible with all
queries that don't specifically require these raw binary strings.
Follow-up to recent work in commit 122376f0. There still hasn't been a
stable release with the pg_get_wal_block_info function, so no bump in
the pg_walinspect extension version.
Per suggestion from Melanie Plageman.
Author: Peter Geoghegan <pg@bowt.ie>
Discussion: https://postgr.es/m/CAAKRu_bJvbcYBRj2cN6G2xV7B7-Ja+pjTO1nEnEhRR8OXYiABA@mail.gmail.com
Discussion: https://postgr.es/m/CAH2-Wzm9shOkEDM10_+qOZkRSQhKVxwBFiehH6EHWQQRd_rDPw@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions