Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Probably, turning fsync off would be helpful, since you know it is
read-only.

> -----Original Message-----
> From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-
> owner@xxxxxxxxxxxxxx] On Behalf Of Bruce Momjian
> Sent: Monday, April 25, 2005 3:01 PM
> To: David Parker
> Cc: postgres general
> Subject: Re:  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@xxxxxxxxxxxxxxxx               |  (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@xxxxxxxxxxxxxx

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux