Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Prepared Statements vs. pgbouncer
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Paul Lindner <lindner(at)inuus(dot)com>
- Cc: Oliver Jowett <oliver(at)opencloud(dot)com>, pgsql-jdbc(at)postgresql(dot)org
- Subject: Re: Prepared Statements vs. pgbouncer
- Date: Fri, 28 Sep 2007 22:31:36 -0400
- Message-id: <24584.1191033096@sss.pgh.pa.us> <text/plain>
Paul Lindner <lindner(at)inuus(dot)com> writes: > It seems that the driver should immediately deallocate the server-side > prepared statements it creates for cursors when it finishs fetching > data for that cursor. What exactly is the argument here? That no client should use anything more than the fraction of the FE/BE protocol that pgbouncer currently supports? Pardon me for not buying into it. regards, tom lane
- Follow-Ups:
- Re: Prepared Statements vs. pgbouncer
- From: Paul Lindner
- Re: Prepared Statements vs. pgbouncer
- References:
- Prepared Statements vs. pgbouncer
- From: Paul Lindner
- Re: Prepared Statements vs. pgbouncer
- From: Oliver Jowett
- Re: Prepared Statements vs. pgbouncer
- From: Paul Lindner
- Prepared Statements vs. pgbouncer
- Prev by Date: Re: Prepared Statements vs. pgbouncer
- Next by Date: Re: Prepared Statements vs. pgbouncer
- Previous by thread: Re: Prepared Statements vs. pgbouncer
- Next by thread: Re: Prepared Statements vs. pgbouncer
- Indexes: