Re: [HACKERS] Prelim specs for parser hooks for plpgsql

2009/10/22 Itagaki Takahiro : > > Tom Lane 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) > >

Re: [HACKERS] Prelim specs for parser hooks for plpgsql

Tom Lane 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

[HACKERS] Prelim specs for parser hooks for plpgsql

Here's what I'm thinking of doing to enable plpgsql to resolve variable references during the main SQL parser processing, instead of its current hack of replacing references with $n in advance: 1. Add some fields to ParseState to carry hook function pointers as well as "void *" passthrough argumen