Re: rollback vs. commit for closing read-only transaction - Mailing list pgsql-general

From Richard_D_Levine@Raytheon.com
Subject Re: rollback vs. commit for closing read-only transaction
Date
Msg-id OF9DE23174.03AB465F-ON05256FEF.00491713-05256FEF.004940BB@ftw.us.ray.com
Whole thread Raw
In response to Re: rollback vs. commit for closing read-only transaction  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
For portability's sake commit successful transactions and rollback those
that fail.

Rick

pgsql-general-owner@postgresql.org wrote on 04/25/2005 05:53:11 PM:

> "Dann Corbit" <DCorbit@connx.com> writes:
> > Probably, turning fsync off would be helpful, since you know it is
> > read-only.
>
> Wouldn't make any difference: a transaction that hasn't modified the
> database doesn't bother to write any commit/abort WAL record at all.
>
>          regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly


pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: savepoints
Next
From: Rich Shepard
Date:
Subject: Re: Migrating MySQL app to postgres?