diff options
| author | Peter Geoghegan <pg@bowt.ie> | 2023-03-28 10:53:48 -0700 |
|---|---|---|
| committer | Peter Geoghegan <pg@bowt.ie> | 2023-03-28 10:53:48 -0700 |
| commit | bade01cb4dd88f63bd9024cfdaec3d5001a805f3 (patch) | |
| tree | f0cd51f78e3583caece9692da8903e7d69409155 /src/backend/commands/dbcommands.c | |
| parent | 326a33a289c7ba2dbf45f17e610b7be98dc11f67 (diff) | |
| download | postgresql-bade01cb4dd88f63bd9024cfdaec3d5001a805f3.tar.gz postgresql-bade01cb4dd88f63bd9024cfdaec3d5001a805f3.zip | |
Fix recent pg_walinspect fpi_length bug.
Commit 0276ae42dd taught pg_walinspect's pg_get_wal_record_info()
function to output NULLs rather than empty strings for its record
description and block_ref output parameters. However, it inadvertently
moved the function call that sets fpi_length until after it was already
set. As a result, pg_get_wal_record_info() always output spurious
fpi_length values of 0.
Fix by switching the order back (but keep the behavioral change).
Author: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Discussion: https://postgr.es/m/CAH2-WzkJmgSYkt6-smQ+57SxSmov+EKqFZdSimFewosoL_JKoA@mail.gmail.com
Diffstat (limited to 'src/backend/commands/dbcommands.c')
0 files changed, 0 insertions, 0 deletions