| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: security label support, part.2 |
| Date: | 2010-08-22 16:56:58 |
| Message-ID: | 1282496218.13679.2.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tis, 2010-08-17 at 20:04 -0400, Stephen Frost wrote:
> What I'm thinking of is something like a warning if the permissions on
> the child don't match those of the parent when the relationship is
> created, or maybe forcibly setting the permissions on the child (with
> a
> NOTICE), so it's at least clear what is going on. Or perhaps, set the
> permissions on the child only if it doesn't have permissions (with the
> NOTICE), and issue a WARNING if the child already has permissions set.
> Perhaps also a WARNING if someone changes the permissions on a child
> after the relationship has been created too, but let it happen in case
> someone really wants it..
I think there are perfectly good reasons to have different permissions
on parent and child tables. I don't see any reason to monkey around
with that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2010-08-22 17:53:11 | Re: pg_archivecleanup debug message consistency |
| Previous Message | Bruce Momjian | 2010-08-22 16:51:47 | Re: Return of the Solaris vacuum polling problem -- anyone remember this? |