From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [HACKERS] read-only database |
Date: | 2005-05-07 02:10:12 |
Message-ID: | 200505070210.j472ACE16072@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > It seems server_read_only is the same as default_transaction_read_only
> > except it can't be changed.
>
> I thought the TODO item was for a low-level read-only option, suitable
> for trying to look at a corrupted database or run off a read-only volume.
> This is very far from being that --- it allows temp table creation/use,
> and it still eats transaction IDs so it is certainly not read-only to
> xlog or clog.
>
> I am not sure I see any use case for this implementation: it is
> read-only enough to get in your way, without being read-only enough
> to derive any real benefit.
I am not sure I see the use case either but I developed it so everyone
could look at it and decide if it is useful. When true, it is basically
a unchangable default_transaction_read_only.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-05-07 02:57:59 | Re: Patch for collation using ICU |
Previous Message | Alvaro Herrera | 2005-05-07 01:17:58 | Re: rendezvous |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-05-07 02:22:47 | Re: COPY CSV header line feature |
Previous Message | Tom Lane | 2005-05-06 23:35:31 | Re: [HACKERS] read-only database |