Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Prepared Statements vs. pgbouncer
- From: Oliver Jowett <oliver(at)opencloud(dot)com>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Paul Lindner <lindner(at)inuus(dot)com>, pgsql-jdbc(at)postgresql(dot)org
- Subject: Re: Prepared Statements vs. pgbouncer
- Date: Sat, 29 Sep 2007 16:49:25 +1200
- Message-id: <46FDD955.80204@opencloud.com> <text/plain>
Tom Lane wrote:
I'm kinda hijacking the thread here, because this question is unrelated to pgbouncer's behavior, but: have you ever done any performance measurement to prove that preparing BEGIN/COMMIT/ROLLBACK is a good idea?
No benchmarks. There would be essentially no difference in the driver code either way (literally, you'd have to add code to avoid preparing the statement) so unless named statements are much more expensive than unnamed ones it's probably not worth worrying about. We do avoid processing an extra network message each way (Parse/ParseComplete) with the current code.
-O
- Follow-Ups:
- Re: Prepared Statements vs. pgbouncer
- From: Tom Lane
- 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
- Re: Prepared Statements vs. pgbouncer
- From: Oliver Jowett
- Re: Prepared Statements vs. pgbouncer
- From: Tom Lane
- 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: