| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | <simon(at)2ndquadrant(dot)com>,<drkp(at)csail(dot)mit(dot)edu>, <pgsql-hackers(at)postgresql(dot)org>, <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |
| Date: | 2011-06-07 17:42:02 |
| Message-ID: | 4DEE1C9A020000250003E27D@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> It makes me a bit uncomfortable to do catalog cache lookups while
> holding all the lwlocks.
I think I've caught up with the rest of the class on why this isn't
sane in DropAllPredicateLocksFromTableImpl, but I wonder about
CheckTableForSerializableConflictIn. We *do* expect to be throwing
errors in here, and we need some way to tell whether an index is
associated with a particular heap relation. Is the catalog cache
the right way to check that here, or is something else more
appropriate?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2011-06-07 17:42:46 | Re: BUG #6041: Unlogged table was created bad in slave node |
| Previous Message | Andrew Dunstan | 2011-06-07 17:40:21 | Re: [Pgbuildfarm-members] CREATE FUNCTION hang on test machine polecat on HEAD |