Re: bugs

Yes, right now references constraints require update
permissions on the table being referenced in order
to grab row level locks on it with SELECT FOR UPDATE.

Stephan Szabo
sszabo(at)bigpanda(dot)com

On Thu, 31 Aug 2000, Alexei E. Korneyev wrote:

> ============================================================================
> POSTGRESQL BUG REPORT TEMPLATE
> ============================================================================
>
>
> Your name : Alexei E. Korneyev
> Your email address : alexei(at)niva(dot)sposad(dot)ru
>
>
> System Configuration
> ---------------------
> Architecture : Intel Pentium II
>
> Operating System : Linux RedHat 2.2.12
>
> PostgreSQL version : PostgreSQL-7.0.2
>
> Compiler used : uncnown Build Host: utility.wgcr.org
>
>
> Please enter a FULL description of your problem:
> ------------------------------------------------
> i create this:
>
> ------------------------
> create table "users" (
> name varchar(10) PRIMARY KEY
> );
> create table "stat" (
> peername varchar(10) REFERENCES users(name)
> );
>
> revoke ALL on stat,users from PUBLIC;
> grant INSERT, SELECT on stat to statist;
> grant select on users to statist;
> grant ALL on stat to basemaster;
> insert into users values('niva');
> insert into stat values ('niva',abstime('now'),timespan(0),8607272,1829436);
> ---------------------
> After that I do(make) connection as the user statis and execute cmd:
> -----------------------
> insert into stat
> values('niva',abstime('now'),timespan(abstime('now')-(select max(timewrite)
> from stat)),50,50);";
> --------------------------
> server say:Access deny on users...
>
> After I change the rights on:
>
> grant select,update on users to statist;
>
> ,the query exec successfully
>
>
> Alexei E. Korneyev
> aek(at)tsinet(dot)ru
>