From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:37:44 |
Message-ID: | 20070905153744.GF6102@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Owen Hartnett wrote:
> >> I've been able to turn on statement logging (I've set log_statement to
> >> 'all'), but it doesn't seem to show the begin transaction - commit -
> >> rollback statements. Is there another way to have them show up in the log?
>
> > If they don't show up, they are not being executed at all; which
> > explains why your transactions "don't roll back", because there are no
> > transaction blocks defined at all.
>
> 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?
--
Alvaro Herrera http://www.advogato.org/person/alvherre
"¿Cómo puedes confiar en algo que pagas y que no ves,
y no confiar en algo que te dan y te lo muestran?" (Germán Poo)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-09-05 15:52:01 | Re: problem with transactions in VB.NET using npgsql |
Previous Message | Tom Lane | 2007-09-05 15:32:04 | Re: problem with transactions in VB.NET using npgsql |