Quick Links

Re: Refactor how we form HeapTuples for CatalogTuple(Insert|Update)

From:	Andres Freund <andres(at)anarazel(dot)de>
To:	Greg Burd <greg(at)burd(dot)me>
Cc:	PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject:	Re: Refactor how we form HeapTuples for CatalogTuple(Insert\|Update)
Date:	2026-01-30 17:20:01
Message-ID:	6izworhewgnye3f3yvqmmaacx67djjsb3nerd2eei2v6mopzhk@ll2jfwsnusy6
Views:	Whole Thread \| Raw Message \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

Hi,

Sorry for being a downer - but: Is the gain here really worth the squeeze?
This is a *lot* of changes just to avoid a bunch of comparisons when doing
catalog changes.

Greetings,

Andres Freund

In response to

Re: Refactor how we form HeapTuples for CatalogTuple(Insert|Update) at 2026-01-29 16:39:34 from Greg Burd

Responses

Re: Refactor how we form HeapTuples for CatalogTuple(Insert|Update) at 2026-01-30 18:22:56 from Greg Burd

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Álvaro Herrera	2026-01-30 17:42:27	Re: Set 1s WaitLatch timeout if standby limit has expired in ResolveRecoveryConflictWithBufferPin
Previous Message	Andres Freund	2026-01-30 17:11:44	Re: More speedups for tuple deformation