From: | "Dann Corbit" <DCorbit(at)connx(dot)com> |
---|---|
To: | "David Parker" <dparker(at)tazznetworks(dot)com> |
Cc: | "postgres general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: rollback vs. commit for closing read-only transaction |
Date: | 2005-04-25 22:04:35 |
Message-ID: | D425483C2C5C9F49B5B7A41F89441547055B04@postal.corporate.connx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Probably, turning fsync off would be helpful, since you know it is
read-only.
> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-
> owner(at)postgresql(dot)org] On Behalf Of Bruce Momjian
> Sent: Monday, April 25, 2005 3:01 PM
> To: David Parker
> Cc: postgres general
> Subject: Re: [GENERAL] rollback vs. commit for closing read-only
> transaction
>
> David Parker wrote:
> > If an application transaction is known to be read-only, is there any
> > reason to prefer COMMIT or ROLLBACK for closing that transaction?
Would
> > there be any performance difference between the two commands?
>
> Doesn't matter.
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania
> 19073
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
majordomo(at)postgresql(dot)org
From | Date | Subject | |
---|---|---|---|
Next Message | Typing80wpm | 2005-04-25 22:27:54 | pgexplorer adm |
Previous Message | Bruce Momjian | 2005-04-25 22:00:59 | Re: rollback vs. commit for closing read-only transaction |