> ... 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 it seemed
to prepare it everywhere... oh well.
Either way, it avoids the problem with prepared queries in that you
cannot know in advance if your query has already been prepared or not.
In response to
pgsql-hackers by date
|Next:||From: Christopher Browne||Date: 2005-01-25 12:03:28|
|Subject: Re: Much Ado About COUNT(*)|
|Previous:||From: ITAGAKI Takahiro||Date: 2005-01-25 10:33:40|
|Subject: Re: WAL: O_DIRECT and multipage-writer|
pgsql-odbc by date
|Next:||From: fbbsantos||Date: 2005-01-25 16:49:09|
|Subject: ODBC (win32) X PostgreSQL(Linux)|
|Previous:||From: Neil Conway||Date: 2005-01-25 10:19:46|
|Subject: Re: [HACKERS] RQ: Prepared statements used by multiple connections|