new postgresql.conf - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject new postgresql.conf
Date
Msg-id 02bb01c354b1$838175b0$2800a8c0@mars
Whole thread Raw
Responses Re: new postgresql.conf  (Gavin Sherry <swm@linuxworld.com.au>)
Re: new postgresql.conf  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Just saw these:

#default_transaction_isolation = 'read committed'
#default_transaction_read_only = false

Does the second option control the new read only transaction mode?  I
thought 'read only' was just a new level of transaction isolation (ie. one
of the 4 sql standard ones), so why does it need its own GUC var?

Chris



pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: followup on previous
Next
From: Gavin Sherry
Date:
Subject: Re: new postgresql.conf