| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | lei yang <yanglei(dot)ovo(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] The heap_getsysattr function deletes unused parameters |
| Date: | 2026-07-16 04:33:50 |
| Message-ID: | alhfLjwWUMgybNOD@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 15, 2026 at 11:53:40AM -0400, Tom Lane wrote:
> I do not think this is a great idea. We don't use the tupdesc today
> perhaps, but it's plausible that it'd be needed in the future.
> Different table AMs might have different sets of system columns.
>
> Unless you can show a measurable performance gain from this change,
> we should leave it alone.
One thing that may make this removal worth it would be to look at if
heap_getsysattr() is used in some extension outside of the core code
and see if these removals lead to some simplifications with the
TupleDescs involved (say for example less locks required). The
in-core callers of heap_getsysattr() don't make that perspective
really attractive.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-07-16 04:34:58 | Re: Improve pg_stat_statements scalability |
| Previous Message | Amit Kapila | 2026-07-16 04:28:41 | Re: sequencesync worker race with REFRESH SEQUENCES |