Re: [HACKERS] read-only database - Mailing list pgsql-patches

From Hannu Krosing
Subject Re: [HACKERS] read-only database
Date
Msg-id 1116410847.4809.23.camel@fuji.krosing.net
Whole thread Raw
In response to Re: [HACKERS] read-only database  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-patches
On E, 2005-05-09 at 20:21 -0700, Joshua D. Drake wrote:
> > 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.

Would it still not have the same issues as Slony (one can create new
tables) this patch (one can create temp tables) ?

--
Hannu Krosing <hannu@tm.ee>

pgsql-patches by date:

Previous
From: Hannu Krosing
Date:
Subject: PATCH to allow concurrent VACUUMs to not lock each other out from cleaning old tuples
Next
From: Alvaro Herrera
Date:
Subject: Re: Refactoring in lock.c