On Tue, 2010-09-07 at 14:49 -0700, David Fetter wrote:
> There are two problems at hand here, as I see it: the more general
> problem of "freezing" settings for a given role, and the very specific
> capability of guaranteeing read-only-ness, which could have large
> implications in, for example, data warehousing and replication
> systems.
>
> Should we just call them separate problems, look into how to approach
> the latter one, and table the former?
That sounds like a good plan. Right now, the only solid use case we have
is "read only role", and it's difficult to build a (good) general
mechanism from a single use case.
Regards,
Jeff Davis
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
