| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] read-only database |
| Date: | 2005-05-10 03:21:26 |
| Message-ID: | 428028B6.70000@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> As I mentioned before, I wanted to the read-only database mode.
> It is the per-database state.
>
> http://archives.postgresql.org/pgsql-hackers/2005-03/msg00540.php
>
> However, if it is not provided, we have to find alternative way
> to get our purpose.
>
> So I'm still looking for how to make the (user) database as read-only.
>
Mammoth PostgreSQL Replicator could do this. If you set a database to a
slave and tell it to be a slave for all tables it would be read only.
Sincerely,
Joshua D. Drake
Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2005-05-10 03:34:22 | Re: Oracle Style packages on postgres |
| Previous Message | Tom Lane | 2005-05-10 03:20:15 | Re: Inline PL/pgSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2005-05-10 04:14:33 | pgstat: reduce message header |
| Previous Message | Satoshi Nagayasu | 2005-05-10 03:18:10 | Re: [HACKERS] read-only database |