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

2005-04-26 Thread Richard_D_Levine
For portability's sake commit successful transactions and rollback those
that fail.

Rick

[EMAIL PROTECTED] wrote on 04/25/2005 05:53:11 PM:

> "Dann Corbit" <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] so that your
>   message can get through to the mailing list cleanly


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


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

2005-04-25 Thread Tom Lane
"Dann Corbit" <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly


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

2005-04-25 Thread Dann Corbit
Probably, turning fsync off would be helpful, since you know it is
read-only.

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] 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@candle.pha.pa.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
[EMAIL PROTECTED]

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

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


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

2005-04-25 Thread Bruce Momjian
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@candle.pha.pa.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 [EMAIL PROTECTED]