From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Artur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>, Robert Haas <robertmhaas(at)gmail(dot)com>, Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Victor Wagner <vitus(at)wagner(dot)pp(dot)ru>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
Subject: | Re: [PATCH] Generic type subscription |
Date: | 2017-02-05 10:28:51 |
Message-ID: | CA+q6zcWA8asrs66Y_zpW2NRN_HP5xnpbJ4kLEziKOE3NOFVLow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 24 January 2017 at 02:36, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It might be possible to get away with having only one pg_type column,
> pointing at the parse-analysis function. That function would generate
> a SubscriptingRef tree node containing the OID of the appropriate
> execution function, which execQual.c could call without ever knowing
> its name explicitly.
Btw, is it acceptable if such generated SubscriptingRef will contain just a
function pointer to the appropriate execution function instead of an OID
(e.g.
like `ExprStateEvalFunc`)? It will help to avoid problems in case of
extensions.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2017-02-05 10:35:17 | Re: Draft release notes for next week's releases are up for review |
Previous Message | Pavel Stehule | 2017-02-05 09:53:32 | Re: Index corruption with CREATE INDEX CONCURRENTLY |