Re: Solution for RI permission problem

As a question, since I don't have a source tree available here at work,
will there be an issue if an elog occurs between the various two user id
sets? Just wondering, because most of those statements are do some
SPI thing or elog.

Stephan Szabo
sszabo(at)bigpanda(dot)com

On Wed, 20 Sep 2000, Peter Eisentraut wrote:

> Here's what I've come up with to avoid "permission denied" errors when a
> RI trigger has to lock a PK table. Whenever the SELECT FOR UPDATE is
> executed I temporarily switch the current user id to the owner of the PK
> table. It's not the grand unified solution via setuid functions that was
> envisioned now and then, but it does the same conceptually. For a
> terminally elegant solution I can only suggest not using the SPI
> interface.
>
> I recommend this patch to be checked out by someone knowledgeable in the
> RI area.