Re: SIREAD lock versus ACCESS EXCLUSIVE lock - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: SIREAD lock versus ACCESS EXCLUSIVE lock
Date
Msg-id 4DEDFD76020000250003E26D@gw.wicourts.gov
Whole thread Raw
In response to Re: SIREAD lock versus ACCESS EXCLUSIVE lock  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>> What am I missing?
> 
> Out-of-memory.  Query cancel.  The attempted catalog access
> failing because it results in a detected deadlock.  I could
> probably think of several more if I spent ten minutes on it; and
> that's not even considering genuine problem conditions such as a
> corrupted catalog index, which robustness demands that we not fall
> over completely for.
> 
> You should never, ever assume that an operation as complicated as
> a catalog lookup can't fail.
Got it.  Thanks.
-Kevin


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Range Types and extensions
Next
From: Heikki Linnakangas
Date:
Subject: Re: WALInsertLock tuning