> > ... a prepared version that is local to the backend that invokes the
> > function, yes (i.e. it will be planned once per backend). So ISTM
this
> > is equivalent functionality to what you can get using PREPARE or the
> > extended query protocol.
>
> Are you sure it's only per-backend? I thoug
It looks it couldn't happen this a way.
Did somebody find out an alternative.
Is reasonable some idea based on a connection pool ?
-Bozhidar
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
On Tue, Jan 25, 2005 at 10:36:34AM +, Christopher Kings-Lynne wrote:
> >
> >... a prepared version that is local to the backend that invokes the
> >function, yes (i.e. it will be planned once per backend). So ISTM this
> >is equivalent functionality to what you can get using PREPARE or the
>
... a prepared version that is local to the backend that invokes the
function, yes (i.e. it will be planned once per backend). So ISTM this
is equivalent functionality to what you can get using PREPARE or the
extended query protocol.
Are you sure it's only per-backend? I thought I tested it and
Christopher Kings-Lynne wrote:
I need a mechanism to keep my queries in optimized state so that
multiple processes can use them.
You should use stored procedures then.
For instance, say you want to keep 'SELECT * FROM table WHERE id=x'
prepared. You would go:
CREATE OR REPLACE FUNCTION get_tab
I need a mechanism to keep my queries in optimized
state so that multiple processes can use them.
You should use stored procedures then.
For instance, say you want to keep 'SELECT * FROM table WHERE id=x'
prepared. You would go:
CREATE OR REPLACE FUNCTION get_table_id(integer) RETURNS SETOF tab
Hi all !
I need a mechanism to keep my queries in optimized
state so that multiple processes can use them.
__
Do you Yahoo!?
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250
-
