Date: Tue, 17 Nov 1998 20:30:09 +0100
From: Michael Meskes <meskes@usa.net>
To: pgsql-hackers@hub.org
Subject: Re: [HACKERS] PREPARE
Message-ID: <19981117203009.E1442@usa.net>
Mail-Followup-To: pgsql-hackers@hub.org
References: <000501be119e$6c16efa0$8a14f7d0@taral.dobiecenter.com>
	<19981117101824.C2181@usa.net>
	<36517DEF.7989C4EC@alumni.caltech.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <36517DEF.7989C4EC@alumni.caltech.edu>;
	from Thomas G. Lockhart on Tue, Nov 17, 1998 at 01:45:19PM +0000

On Tue, Nov 17, 1998 at 01:45:19PM +0000, Thomas G. Lockhart wrote:
> So what would it take to do this in the backend? I think the places
> which would need to be touched fall into areas I either know about or am
> starting to look at to implement the CASE clause.
> 
> We'd need:
>   - a "named buffer" (or several) to hold the intermediate input

I didn't get this one completly. What input do you mean?

>   - a way to pass in parameters or substitution arguments

Yes. That means changing of declare cursor as well.

>   - a way to decide if previous parser/planner/executor
>     results can be reused

Yes.

> What else?

Running planner on the statement as it is without the variables to be
substituted. So execution of declare gets faster.

Michael
-- 
Dr. Michael Meskes, Manager of the Western Branch Office, Datenrevision GmbH
work: Cuxhavener Str. 36, D-21149 Hamburg
home: Th.-Heuss-Str. 61,  D-41812 Erkelenz, Michael.Meskes@usa.net
Go SF49ers! Go Rhein Fire! Use Debian GNU/Linux!