Re: rollback vs. commit for closing read-only transaction
От | Dann Corbit |
---|---|
Тема | Re: rollback vs. commit for closing read-only transaction |
Дата | |
Msg-id | D425483C2C5C9F49B5B7A41F89441547055B04@postal.corporate.connx.com обсуждение исходный текст |
Ответ на | rollback vs. commit for closing read-only transaction ("David Parker" <dparker@tazznetworks.com>) |
Ответы |
Re: rollback vs. commit for closing read-only transaction
|
Список | pgsql-general |
Probably, turning fsync off would be helpful, since you know it is read-only. > -----Original Message----- > From: pgsql-general-owner@postgresql.org [mailto:pgsql-general- > owner@postgresql.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@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 majordomo@postgresql.org
В списке pgsql-general по дате отправления: