| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, Dennis Sacks <dennis(at)illusions(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: lots of puzzling log messages |
| Date: | 2005-04-24 00:20:55 |
| Message-ID: | 24219.1114302055@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Kris Jurka <books(at)ejurka(dot)com> writes:
> The latest driver will do that as well, but in two statements now that
> transaction end doesn't automatically start a new one immediately. The
> difference is that the server doesn't log it for the 8.0 driver because
> it prepares the begin/commit/rollback statements just once and executes
> them from then on.
Hmm. ISTM the value of preparing a utility statement like begin/commit/
rollback would be minuscule at best. Is there a reason for not just
issuing those as plain queries?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas F.O'Connell | 2005-04-24 03:23:56 | Re: Table modifications with dependent views - best practices? |
| Previous Message | Tom Lane | 2005-04-24 00:19:31 | Re: Had a problem with pg_clog |