Re: [HACKERS] PREPARE - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] PREPARE
Date
Msg-id 36517DEF.7989C4EC@alumni.caltech.edu
Whole thread Raw
In response to PREPARE  ("Taral" <taral@cyberjunkie.com>)
Responses Re: [HACKERS] PREPARE  (Bruce Momjian <maillist@candle.pha.pa.us>)
Re: [HACKERS] PREPARE  (Michael Meskes <meskes@usa.net>)
List pgsql-hackers
> I'm still holding back PREPARE for ecpg until I can think of a
> good solution. The best of course would be in the backend.

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 - a way to pass in parameters or substitution
arguments- a way to decide if previous parser/planner/executor   results can be reused
 

What else?
                       - Tom


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] More PostgreSQL+CORBA
Next
From: Terry Mackintosh
Date:
Subject: Re: [HACKERS] Tree type, how best to impliment?