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

Re: Command Triggers

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Command Triggers
Date: 2011-12-01 19:18:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Thursday, December 01, 2011 07:21:25 PM Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On Tuesday, November 08, 2011 06:47:13 PM Dimitri Fontaine wrote:
> >> exception to that rule would be SELECT INTO and CREATE TABLE AS SELECT,
> >> and my proposal would be to add specific call sites to the functions
> >> I've provided in the attached patch rather than try to contort them into
> >> being a good citizen as a utility command.
> > 
> > I would very much prefer to make them utility commands and rip out the
> > executor support for that.
> > Is there something making that especially hard that I overlooked? The
> > infrastructure for doing so seems to be there.
> Well, I think the main problem is going to be shunting the query down
> the right parsing track (SELECT versus utility-statement) early enough.
> Making this work cleanly would be a bigger deal than I think you're
> thinking.
Yes. I forgot how ugly SELECT INTO is...

> But yeah, it would be nicer if the executor didn't have to worry about
> this.  +1 if you're willing to take on the work.
I won't promise anything but I will play around with the grammar and see if I 
find a nice enough way.


In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2011-12-01 20:32:34
Subject: TupleDescInitEntry failing to initialize varlen members
Previous:From: Jim ButtafuocoDate: 2011-12-01 19:09:04
Subject: Re: Postgresql 9.1 replication failing

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