From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: new postgresql.conf |
Date: | 2003-07-28 05:37:37 |
Message-ID: | 27142.1059370657@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> Just saw these:
> #default_transaction_isolation = 'read committed'
> #default_transaction_read_only = false
> Does the second option control the new read only transaction mode?
Yes.
> 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?
No, it's orthogonal to isolation. A read-only transaction could
sensibly want either READ COMMITTED or SERIALIZABLE behavior, depending
on whether it wants to see the effects of commits while it's in progress.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-07-28 05:40:50 | Re: Can't Build 7.3.4 on OS X |
Previous Message | Tom Lane | 2003-07-28 05:23:55 | Re: Make clean fails |