Re: rollback vs. commit for closing read-only transaction

From: Richard_D_Levine(at)Raytheon(dot)com
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Dann Corbit" <DCorbit(at)connx(dot)com>, "David Parker" <dparker(at)tazznetworks(dot)com>, "postgres general" <pgsql-general(at)postgresql(dot)org>, pgsql-general-owner(at)postgresql(dot)org
Subject: Re: rollback vs. commit for closing read-only transaction
Date: 2005-04-26 13:20:06
Message-ID: OF9DE23174.03AB465F-ON05256FEF.00491713-05256FEF.004940BB@ftw.us.ray.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

For portability's sake commit successful transactions and rollback those
that fail.

Rick

pgsql-general-owner(at)postgresql(dot)org wrote on 04/25/2005 05:53:11 PM:

> "Dann Corbit" <DCorbit(at)connx(dot)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(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rich Shepard 2005-04-26 13:24:43 Re: Migrating MySQL app to postgres?
Previous Message Alvaro Herrera 2005-04-26 13:10:17 Re: savepoints