Re: problems with table corruption continued - Mailing list pgsql-hackers

From Stephan Szabo
Subject Re: problems with table corruption continued
Date
Msg-id 20011218173431.C65195-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Re: problems with table corruption continued  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, 18 Dec 2001, Tom Lane wrote:

> The ri_triggers code has a lot of places that open things NoLock,
> but it only looks into the relcache entry and doesn't try to scan
> the relation.  Nonetheless that code bothers me; we could be using
> an obsolete relcache entry if someone has just committed an ALTER
> TABLE on the relation.  Some of the cases may be safe because a lock
> is held higher up (eg, on the table from which the trigger was fired)
> but I doubt they all are.

Probably not, since it looks like that's being done for the other table of
the constraint (not the one on which the trigger was fired).



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Concerns about this release
Next
From: Bruce Momjian
Date:
Subject: Re: Thoughts on the location of configuration files