| From: | Paul Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres Permissions Article |
| Date: | 2017-03-30 20:19:52 |
| Message-ID: | c95aaecb-c3b8-b085-0b34-99d1f22332f1@illuminatedcomputing.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> Also I don't understand why you wrote “You need the permission on both
> tables”: Only the owner of a table can add constraints to it
Ah, this piece was really helpful for me in making it click. Thanks so
much! I added a couple new paragraphs to my post with a link back to
this thread. I feel like it all makes sense now! :-)
FYI "You need this permission on both tables" is what the docs say
(https://www.postgresql.org/docs/9.6/static/sql-grant.html):
> To create a foreign key constraint, it is necessary to have this
privilege on both the referencing and referenced columns.
Maybe it would be worth clarifying there that you need to *own* the
referencing table, and you need REFERENCES on the referenced table?
In any case, thanks again to you all for your help figuring this out!
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-03-30 20:45:55 | REFERENCES privilege should not be symmetric (was Re: Postgres Permissions Article) |
| Previous Message | Tom Lane | 2017-03-30 19:36:40 | Re: pg_dump recording privileges on foreign data wrappers |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-03-30 20:20:21 | Re: [COMMITTERS] pgsql: Default monitoring roles |
| Previous Message | Pavel Stehule | 2017-03-30 19:55:41 | Re: New CORRESPONDING clause design |