diff options
| author | Álvaro Herrera <alvherre@kurilemu.de> | 2025-07-07 22:38:12 +0200 |
|---|---|---|
| committer | Álvaro Herrera <alvherre@kurilemu.de> | 2025-07-07 22:38:40 +0200 |
| commit | 3adcf9fbd8ba9c07edb3ef5168a259fb12e6e3a6 (patch) | |
| tree | dde6c031f743c4333bee220be617d9557f1b379f /contrib/btree_gist/sql | |
| parent | 87b05fdc73e84d6b0bf0e03efad95c99c203cd1f (diff) | |
| download | postgresql-3adcf9fbd8ba9c07edb3ef5168a259fb12e6e3a6.tar.gz postgresql-3adcf9fbd8ba9c07edb3ef5168a259fb12e6e3a6.zip | |
Adapt pg_upgrade test to pg_lsn output format difference
Commit 2633dae2e487 added some zero padding to various LSNs output
routines so that the low word is always 8 hex digits long, for easy
human consumption. This included the pg_lsn datatype, which breaks the
pg_upgrade test when it compares the pg_dump output of an older version.
Silence this problem by setting the pg_lsn columns to NULL before the
upgrade.
Discussion: https://postgr.es/m/202507071504.xm2r26u7lmzr@alvherre.pgsql
Diffstat (limited to 'contrib/btree_gist/sql')
0 files changed, 0 insertions, 0 deletions