(BTom Lane wrote:
(B> I'd view this as a postmaster state that propagates to backends.
(B> Probably you'd enable it by means of a postmaster option, and the
(B> only way to get out of it is to shut down and restart the postmaster
(B> without the option.
(B
(BI've created a patch to make a p
On Thu, 2005-03-17 at 12:40 +0900, Satoshi Nagayasu wrote:
> Tom Lane wrote:
> >>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.
>
> I see.
>
> Thanks for comment
Tom Lane wrote:
(B>>I saw Oracle's reference manual, and found ALTER DATABASE OPEN READ ONLY
(B>>command
(B>>to make a stand-by database.
(B>
(B> Perhaps, but that's *not* what the TODO item is about.
(B
(BI see.
(B
(BThanks for comments.
(B--
(BNAGAYASU Satoshi <[EMAIL PROTECTED]>
(
Satoshi Nagayasu <[EMAIL PROTECTED]> 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 fo
Tom Lane wrote:
(B> Uh, no, because changing that would by definition not be a read-only
(B> operation. Therefore there'd be no way to enter the read-only state,
(B> and definitely no way to get out of it again.
(B
(BI saw Oracle's reference manual, and found ALTER DATABASE OPEN READ ONLY com
Satoshi Nagayasu <[EMAIL PROTECTED]> writes:
>> * Allow a warm standby system to also allow read-only queries
> Does anyone have any plan to work on this?
> I think we need to extend the pg_database catalog to
> have a database state (read-only or writable),
> and also need to extend ALTER DATABA
