Re: [HACKERS] RQ: Prepared statements used by multiple connections

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Bojidar Mihajlov <bmihajlov(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org
Subject: Re: [HACKERS] RQ: Prepared statements used by multiple connections
Date: 2005-01-25 10:36:34
Message-ID: 41F62132.6070403@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-odbc

> ... 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.

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Browne 2005-01-25 12:03:28 Re: Much Ado About COUNT(*)
Previous Message ITAGAKI Takahiro 2005-01-25 10:33:40 Re: WAL: O_DIRECT and multipage-writer

Browse pgsql-odbc by date

  From Date Subject
Next Message fbbsantos 2005-01-25 16:49:09 ODBC (win32) X PostgreSQL(Linux)
Previous Message Neil Conway 2005-01-25 10:19:46 Re: [HACKERS] RQ: Prepared statements used by multiple connections