| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: read-only database |
| Date: | 2005-03-17 03:20:34 |
| Message-ID: | 19603.1111029634@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> writes:
> Tom Lane wrote:
>> Uh, no, because changing that would by definition not be a read-only
>> operation. Therefore there'd be no way to enter the read-only state,
>> and definitely no way to get out of it again.
> I saw Oracle's reference manual, and found ALTER DATABASE OPEN READ ONLY command
> to make a stand-by database.
Perhaps, but that's *not* what the TODO item is about.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Satoshi Nagayasu | 2005-03-17 03:40:24 | Re: read-only database |
| Previous Message | Mark Kirkwood | 2005-03-17 02:53:18 | Re: contrib/pg_buffercache |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Satoshi Nagayasu | 2005-03-17 03:40:24 | Re: read-only database |
| Previous Message | Mark Kirkwood | 2005-03-17 02:53:18 | Re: contrib/pg_buffercache |