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

From Tom Lane
Subject Re: rollback vs. commit for closing read-only transaction
Date
Msg-id 26036.1114469591@sss.pgh.pa.us
Whole thread Raw
In response to Re: rollback vs. commit for closing read-only transaction  ("Dann Corbit" <DCorbit@connx.com>)
Responses Re: rollback vs. commit for closing read-only transaction  (Richard_D_Levine@Raytheon.com)
List pgsql-general
"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

pgsql-general by date:

Previous
From: "Dann Corbit"
Date:
Subject: Re: rollback vs. commit for closing read-only transaction
Next
From: Typing80wpm@aol.com
Date:
Subject: Toad Adm. Datasource Location