| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <simon(at)2ndquadrant(dot)com>,<drkp(at)csail(dot)mit(dot)edu>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |
| Date: | 2011-06-07 15:29:10 |
| Message-ID: | 4DEDFD76020000250003E26D@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-06-07 15:36:29 | Re: WALInsertLock tuning |
| Previous Message | Tom Lane | 2011-06-07 15:15:38 | Re: Range Types and extensions |