Re: Prepared Statements vs. pgbouncer
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Oliver Jowett <oliver(at)opencloud(dot)com>
- 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 00:54:00 -0400
- Message-id: <26029.1191041640@sss.pgh.pa.us> <text/plain>
Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> 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.
I don't have a reason to think it's a big loss --- I was just worried
that you were going out of your way to make this happen, when it's
probably not a win either.
regards, tom lane
Home |
Main Index |
Thread Index