| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Cc: | nagya(at)inf(dot)elte(dot)hu |
| Subject: | Re: PostgreSQL BugTool Submission |
| Date: | 2000-08-23 22:01:36 |
| Message-ID: | Pine.BSF.4.10.10008231447210.28545-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Yes, this is a known issue due to the fact that the
triggers use SPI and need to use SELECT ... FOR UPDATE
to lock the rows it is reading (and select for update
requires the update permission). The workaround I
know about for now is to give update permission and make
triggers to disallow updates as appropriate.
(If this isn't in the TODO list or FAQ yet, it probably
should be.)
Stephan Szabo
sszabo(at)bigpanda(dot)com
On Wed, 23 Aug 2000 pgsql-bugs(at)postgresql(dot)org wrote:
> NAGY Andras (nagya(at)inf(dot)elte(dot)hu) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> Foreign keys referencing read-only tables fail
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql-bugs | 2000-08-24 00:52:05 | PostgreSQL BugTool Submission |
| Previous Message | pgsql-bugs | 2000-08-23 21:53:13 | PostgreSQL BugTool Submission |