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

Re: pgsql: PREPARE and EXPLAIN need to copy the source query just like we

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sean Chittenden <sean(at)chittenden(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: PREPARE and EXPLAIN need to copy the source query just like we
Date: 2004-12-13 00:45:51
Message-ID: 13819.1102898751@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committers
Sean Chittenden <sean(at)chittenden(dot)org> writes:
>> PREPARE and EXPLAIN need to copy the source query just like we recently
>> had to do in DECLARE CURSOR.  AFAICS these are all the places affected.
>> PREPARE case per example from Michael Fuhr, EXPLAIN case located by
>> grepping for planner calls ...

> Does this mean that cache lookup failures (most notably in pl/pgsql) 
> will simply result in a replan as opposed to a query failure and the 
> transaction being aborted?  Or is this a first step in that direction?  

No, and no.  This has no user-visible impact at all (other than not
crashing in cases that should work).

			regards, tom lane

In response to

pgsql-committers by date

Next:From: Bruce MomjianDate: 2004-12-13 03:37:10
Subject: pgsql: Update FAQ.
Previous:From: Tom LaneDate: 2004-12-13 00:33:19
Subject: pgsql: Avoid generating excess (and illegal) parentheses around an

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