Skip site navigation (1) Skip section navigation (2)

Re: EXPLAIN, utility statement parameters, and recent plpgsql changes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: EXPLAIN, utility statement parameters, and recent plpgsql changes
Date: 2010-01-14 20:42:37
Message-ID: 29262.1263501757@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Dimitri Fontaine <dfontaine(at)hi-media(dot)com> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> Well, the point of the hook is to change the results of parse
>> transformation, so just calling it doesn't do much --- you have to apply
>> the whole parse analysis process, *and keep the resulting tree*.

> Could that be done in the function, in the phase you call "doing initial
> parsing"?

Within copyParamList?  Seems like rather an abuse of the design ... it's
just supposed to copy the ParamListInfo, not editorialize on the entire
content of the portal.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Jonas JDate: 2010-01-14 20:51:24
Subject: Re: dbt2-shell script problem
Previous:From: Kevin GrittnerDate: 2010-01-14 20:23:01
Subject: Re: Testing with concurrent sessions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group