Re: Commit 86dc90056 - Rework planning and execution of UPDATE and DELETE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Langote <amitlangote09(at)gmail(dot)com>
Subject: Re: Commit 86dc90056 - Rework planning and execution of UPDATE and DELETE
Date: 2021-04-19 14:34:00
Message-ID: 217262.1618842840@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> writes:
> With the commit mentioned in the $subject, I am seeing the
> change in behaviour with the varlena header size.

Interesting. AFAICS, the new behavior is correct and the old is wrong.
SET STORAGE PLAIN is supposed to disable use of TOAST features, including
short varlena headers. So now that's being honored by the UPDATE, but
before it was not. I have no idea exactly why that changed though ---
I'd expect that to be implemented in low-level tuple-construction logic
that the planner rewrite wouldn't have changed.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2021-04-19 14:34:27 Re: Commit 86dc90056 - Rework planning and execution of UPDATE and DELETE
Previous Message Dave Page 2021-04-19 14:26:46 Re: Windows default locale vs initdb