| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Oliver Crosby <ryusei(at)gmail(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Looking for tips |
| Date: | 2005-07-19 19:16:31 |
| Message-ID: | 8613.1121800591@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Oliver Crosby <ryusei(at)gmail(dot)com> writes:
>> You could possibly get some improvement if you can re-use prepared plans
>> for the queries; but this will require some fooling with the client code
>> (I'm not sure if DBD::Pg even has support for it at all).
> Aye. We have prepared statements.
Ah, but are they really prepared, or is DBD::Pg faking it by inserting
parameter values into the query text and then sending the assembled
string as a fresh query? It wasn't until about 7.4 that we had adequate
backend support to let client libraries support prepared queries
properly, and I'm unsure that DBD::Pg has been updated to take advantage
of that support.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Petrilli | 2005-07-19 19:22:07 | Re: Impact of checkpoint_segments under continual load conditions |
| Previous Message | PFC | 2005-07-19 19:14:04 | Re: Looking for tips |