| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: In PrepareToInvalidateCacheTuple, don't force initialization of |
| Date: | 2008-03-05 17:01:33 |
| Message-ID: | 20080305170133.6174C754108@cvs.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
In PrepareToInvalidateCacheTuple, don't force initialization of catalog
caches that we don't actually need to touch. This saves some trivial
number of cycles and avoids certain cases of deadlock when doing concurrent
VACUUM FULL on system catalogs. Per report from Gavin Roy.
Backpatch to 8.2. In earlier versions, CatalogCacheInitializeCache didn't
lock the relation so there's no deadlock risk (though that certainly had
plenty of risks of its own).
Tags:
----
REL8_3_STABLE
Modified Files:
--------------
pgsql/src/backend/utils/cache:
catcache.c (r1.140 -> r1.140.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/cache/catcache.c?r1=1.140&r2=1.140.2.1)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-05 17:01:41 | pgsql: In PrepareToInvalidateCacheTuple, don't force initialization of |
| Previous Message | Tom Lane | 2008-03-05 17:01:26 | pgsql: In PrepareToInvalidateCacheTuple, don't force initialization of |