| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Ensure pg_filenode_relation(0, 0) returns NULL. |
| Date: | 2021-06-12 17:29:45 |
| Message-ID: | E1ls7S5-00086w-4E@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Ensure pg_filenode_relation(0, 0) returns NULL.
Previously, a zero value for the relfilenode resulted in
a confusing error message about "unexpected duplicate".
This function returns NULL for other invalid relfilenode
values, so zero should be treated likewise.
It's been like this all along, so back-patch to all supported
branches.
Justin Pryzby
Discussion: https://postgr.es/m/20210612023324.GT16435@telsasoft.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/1250aad42520fd5a3db68d6381997b7e1f9bb4aa
Modified Files
--------------
src/backend/utils/adt/dbsize.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-06-12 19:12:33 | pgsql: Restore robustness of TAP tests that wait for postmaster restart |
| Previous Message | Tom Lane | 2021-06-12 16:59:33 | pgsql: Don't use Asserts to check for violations of replication protoco |