| From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
|---|---|
| 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 02:48:40 |
| Message-ID: | Pine.LNX.4.21.0307281246240.6308-100000@linuxworld.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 28 Jul 2003, Christopher Kings-Lynne wrote:
> 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?
It is a transaction access mode, not an isolation level. ansi sql supports
two modes: read only and read write.
Gavin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hunter Hillegas | 2003-07-28 03:39:01 | Can't Build 7.3.4 on OS X |
| Previous Message | Christopher Kings-Lynne | 2003-07-28 02:41:32 | followup on previous |