Actually Peter did a patch for this fairly recently I
believe. I haven't grabbed CVS recently enough to know
if it got committed. There's a related question of what
permissions you need to follow referential actions (currently
it's the same permission as if you were doing the implied
statement).
Stephan Szabo
sszabo@bigpanda.com
On Sat, 14 Oct 2000, Bruce Momjian wrote:
> Can someone give me a good description of this for TODO?
>
> >
> > 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@bigpanda.com
> >
> > On Wed, 23 Aug 2000 pgsql-bugs@postgresql.org wrote:
> >
> > > NAGY Andras (nagya@inf.elte.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
> >
> >
>
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
