| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Owen Hartnett <owen(at)clipboardinc(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: problem with transactions in VB.NET using npgsql |
| Date: | 2007-09-05 15:52:01 |
| Message-ID: | 13812.1189007521@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> In PG 8.2 I'd agree, but older versions are not so good about logging
>> execution of prepared statements. What's the server version exactly,
>> and is there any indication of use of prepared statements in the log?
> Humm, but can you prepare BEGIN or COMMIT at all?
At the protocol level you're allowed to prepare anything at all. It
surely is a bit useless to prepare BEGIN or COMMIT, since there's no
plan and no noticeable parse/analyze costs, but I seem to recall seeing
logs suggesting that some client software does so...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2007-09-05 16:26:39 | Re: psql hanging |
| Previous Message | Alvaro Herrera | 2007-09-05 15:37:44 | Re: problem with transactions in VB.NET using npgsql |