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

From: Sean Chittenden <sean(at)chittenden(dot)org>
To: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
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-12 23:18:54
Message-ID: 3131E4B8-4C94-11D9-983C-000A95C705DC@chittenden.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

> 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?
-sc

--
Sean Chittenden

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2004-12-13 00:18:16 pgsql: Back-patch copyOject fix for EXPLAIN/PREPARE.
Previous Message Neil Conway 2004-12-12 22:49:50 pgsql: Add regression tests for the fix committed by Tom for casting