From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | KuroiNeko <evpopkov(at)carrier(dot)kiev(dot)ua> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: select oid .... for update .... |
Date: | 2000-10-15 17:16:32 |
Message-ID: | Pine.BSF.4.10.10010151015460.68379-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
This is a known problem in 7.0.x (see mailing list archives for more
information). Peter E has a patch for 7.1 to remove this problem.
Stephan Szabo
sszabo(at)bigpanda(dot)com
On Sun, 15 Oct 2000, KuroiNeko wrote:
>
> Here's something I don't understand.... If I'm missing an obvious, please
> feel free to kick me in the right direction.
> We're given two tables, linked with a foreign key. When insert is run on a
> master table, everything is OK, when trying to insert into a detail table,
> a strange query appears in the log (schema and log snippet attached).
> In fact, there should be no problem, but if a user has no permissions to
> update the master table (eg, this is a log where he can only insert, but
> neither delete, nor update), then inserting into detail table fails on
> permission violation at the query:
>
> SELECT oid FROM "alpha" WHERE "id" = $1 FOR UPDATE OF "alpha"
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-10-15 18:20:56 | Re: analyze.c |
Previous Message | Tom Lane | 2000-10-15 15:57:32 | Re: AW: ALTER TABLE DROP COLUMN |