From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Getting rid of SQLValueFunction |
Date: | 2022-10-21 05:27:07 |
Message-ID: | Y1Itq9j1xCKaSd4Y@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Oct 21, 2022 at 12:34:23PM +0900, Michael Paquier wrote:
> A sticky point is that this would need the creation of a pg_proc entry
> for "user" which is a generic word, or a shortcut around
> FigureColnameInternal(). The code gain overall still looks appealing
> in the executor, even if we do all that and the resulting backend code
> gets kind of nicer and easier to maintain long-term IMO.
I have looked at that, and the attribute mapping remains compatible
with past versions once the appropriate pg_proc entries are added.
The updated patch set attached does that (with a user() function as
well to keep the code a maximum simple), with more tests to cover the
attribute case mentioned upthread.
--
Michael
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Remove-from-SQLValueFunction-all-the-entries-usin.patch | text/x-diff | 16.1 KB |
v2-0002-Replace-SQLValueFunction-by-direct-function-calls.patch | text/x-diff | 43.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2022-10-21 05:49:26 | Re: TRAP: FailedAssertion("prev_first_lsn < cur_txn->first_lsn", File: "reorderbuffer.c", Line: 927, PID: 568639) |
Previous Message | Kyotaro Horiguchi | 2022-10-21 05:25:57 | Re: thinko in basic_archive.c |