From: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | read-only database |
Date: | 2005-03-16 12:28:17 |
Message-ID: | 42382661.4030001@nttdata.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Hi all,
I've read TODO list in the 8.0.1,
then I'm interested in the following topic.
> * 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 DATABASE command
to change the state.
To make a database read-only, ALTER DATABASE command may change
MyDatabaseReadOnly flag (like XactReadOnly)
and update the pg_database catalog.
If MyDatabaseReadOnly is true, check_xact_readonly() or
ExecCheckXactReadOnly() will prevent from updating the database.
Otherwise, I think we can also prevent from updating the database
around acquiring the XLogInsert lock.
Any ideas? or any suggestions?
--
NAGAYASU Satoshi <nagayasus(at)nttdata(dot)co(dot)jp>
OpenSource Development Center,
NTT DATA Corp. http://www.nttdata.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | strk | 2005-03-16 12:58:44 | Re: caches lifetime with SQL vs PL/PGSQL procs |
Previous Message | David Pradier | 2005-03-16 12:18:24 | Re: Erratic error message "ERROR: column "id_compte" does |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-03-16 12:44:41 | Re: COPY CSV header line feature |
Previous Message | Nicolai Tufar | 2005-03-16 11:36:50 | Re: [pgsql-hackers-win32] snprintf causes regression tests to fail |