Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL BugTool Submission

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, nagya(at)inf(dot)elte(dot)hu
Subject: Re: PostgreSQL BugTool Submission
Date: 2000-10-14 04:36:46
Message-ID: 200010140436.AAA25361@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
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(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
> 
> 


-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

Responses

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2000-10-14 11:06:29
Subject: ORDER BY on INTERSECT
Previous:From: pgsql-bugsDate: 2000-10-13 10:44:49
Subject: Drop table doesn't drop serial sequences.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group