From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org, Vick Khera <vivek(at)khera(dot)org>, Borek Lupomesky <borek(at)lupomesky(dot)cz> |
Subject: | Re: Permission denied when inserting |
Date: | 2011-02-28 17:20:46 |
Message-ID: | 201102280920.47191.adrian.klaver@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Monday, February 28, 2011 9:15:27 am Tom Lane wrote:
> Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> writes:
> > I understand, yet I don't:) Seems I have a misconception of the the
> > FOREIGN KEY process. The error was on the query below, which I am
> > taking is the query you refer to above. To me it looks like a look up
> > from the referencing(permout) table to the referenced(out2cp) one. The
> > part I am not clear on is why that runs with the permissions of the
> > referenced table not the referencing table?
>
> Because we force it that way so that you don't have to splatter
> permissions all around to support a foreign key check. Generally
> the internal FK check queries will only fail if the owner of a table
> revokes his own permissions, which isn't too usual.
>
> regards, tom lane
Had not thought about it from that angle. Thanks.
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Alan Acosta | 2011-02-28 17:43:58 | Lock ACCESS EXCLUSIVE and Select question ! |
Previous Message | Tom Lane | 2011-02-28 17:15:27 | Re: Permission denied when inserting |