| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "Freezing" per-role settings |
| Date: | 2010-09-07 21:59:54 |
| Message-ID: | 1283896794.16596.5.camel@jdavis-ux.asterdata.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Max Bowsher | 2010-09-07 22:10:40 | Re: git: uh-oh |
| Previous Message | David Fetter | 2010-09-07 21:49:43 | Re: "Freezing" per-role settings |