Re: Prelim specs for parser hooks for plpgsql

From: Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Prelim specs for parser hooks for plpgsql
Date: 2009-10-22 01:50:28
Message-ID: 20091022104226.2F3E.52131E4D@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 3. The pre-transform hook would have a signature like
> Node *hook(ParseState *pstate, ColumnRef *cref)
>
> 4. The post-transform hook would have a signature like
> Node *hook(ParseState *pstate, ColumnRef *cref, Node *var)

Are there any relationships between the hooks and
Function Call Hook/parser hook submitted by Pavel-san?
https://commitfest.postgresql.org/action/patch_view?id=160

If we can also use them in normal SQL parsing, they are very useful
to implement SYSDATE global variable for porting from Oracle.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2009-10-22 02:06:11 Re: Controlling changes in plpgsql variable resolution
Previous Message Robert Haas 2009-10-21 21:13:33 Re: Controlling changes in plpgsql variable resolution