From: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SE-PostgreSQL Specifications |
Date: | 2009-07-25 15:53:25 |
Message-ID: | 42DC6C8F-1491-46B6-93C8-9294C49A3763@themactionfaction.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 25, 2009, at 11:06 AM, Tom Lane wrote:
> Sam Mason <sam(at)samason(dot)me(dot)uk> writes:
>> Yes, that seems reasonable. The fact that you're still talking about
>> "confined users" is slightly worrying and would seem to imply that
>> there is still a superuser/normal user divide--it's probably just a
>> terminology thing though.
>
> There had better still be superusers. Or do you want the correctness
> of your backups to depend on whether your SELinux policy is correct?
> The first time somebody loses critical data because SELinux suppressed
> it from their pg_dump output, they're going to be on the warpath.
This behavior is no different than when taking/using an SE-enabled
filesystem backup. And woe to the "admin" who doesn't test his
backups- caveat emptor.
Still, it would be nice if pg_dump warned or stopped if the backup it
created was completely useless (missing data dependencies), no?
Cheers,
M
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2009-07-25 16:15:39 | Re: When is a record NULL? |
Previous Message | Tom Lane | 2009-07-25 15:41:01 | Re: Non-blocking communication between a frontend and a backend (pqcomm) |