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 20:57:40
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:
> 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.
Obviously that depends on the definition of clean...

Changing the grammar to make that explicit seems to involve a bit too many 
changes on a first glance. The cheap way out seems to be to make the decision 
in analyze.c:transformQuery.
Would that be an acceptable way forward?


In response to


pgsql-hackers by date

Next:From: Simon RiggsDate: 2011-12-01 21:02:18
Subject: Re: Command Triggers
Previous:From: Alvaro HerreraDate: 2011-12-01 20:32:34
Subject: TupleDescInitEntry failing to initialize varlen members

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