| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Any reason to keep HEAP_HASOID_OLD? |
| Date: | 2026-10-29 01:02:41 |
| Message-ID: | CAGRkXqRJEEBZs-f2mWtK=r4cbgv-J8tPLXn8k4Hb_Nc+3ujZzQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi David,
Thanks. Keeping t_oid as an always NULL column makes sense to me.
Also leave pageinspect behavior today make sense as well.
Let's go with your patch.
I rechecked the related comments and documents, I think we need to
1. For storage.html, the paragraph after the HeapTupleHeaderData table.
Its first sentence lists "an optional object ID field". The sentences
from "The object ID is only present if the HEAP_HASOID_OLD bit is set"
to the end of the paragraph can go.
2. htup_details.h needs some clean work. the comment still says
"If an OID field is present....."
3. For pageinspect.smgl, it point users to htup_details.h, may add something
like
"t_oid is always NULL. Tuples no longer store an OID, and the column
is kept for compatibility."
Thanks,
Shihao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-10-29 01:16:11 | Re: Reduce logging during prepared transaction recovery |
| Previous Message | Michael Paquier | 2026-10-29 00:50:46 | Re: Return pg_control from pg_backup_stop(). |