| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Andrzej Pilacik <cypisek77(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Strange security issue with Superuser access |
| Date: | 2015-03-10 15:27:47 |
| Message-ID: | CAKFQuwbJosjyUAzMSAm2gQZpg3dcbcafm6Rww_YgN1QL81hDJA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 10, 2015 at 8:20 AM, Andrzej Pilacik <cypisek77(at)gmail(dot)com>
wrote:
> I see the issues that this person might be having. I am not doing a
> restore or working on an existing issue.
>
> My setup is very vanilla, anyone can create these tables and test, will
> get the same permission error... (I did it in a brand new environment)
>
> What I am asking here is why does a SUPERUSER not able to insert the data
> when the constraint is introduced.
>
>
To prevent a super-user from shooting themselves in the foot. Begin
allowed to insert otherwise invalid data is not something that the database
allows a superuser to do. A superuser inserting a NULL into a NOT NULL
column will also get an error. This is no different.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2015-03-10 15:43:21 | Re: Strange security issue with Superuser access |
| Previous Message | Andrzej Pilacik | 2015-03-10 15:20:59 | Re: Strange security issue with Superuser access |