From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Assigning fixed OIDs to system catalogs and indexes |
Date: | 2005-04-18 17:24:21 |
Message-ID: | 200504181724.j3IHOLC00828@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> >> So some changing-oid operations like vacuum full, reindex, etc will not
> >> affect these system catalogs?
>
> > Is it possible to cluster system tables?
>
> No, and yes. CLUSTER, REINDEX, and similar things change the
> relfilenode, not the relation OID.
>
> If you are looking for things that will fundamentally break the system,
> try renaming one of the indexes of a core system catalog ;-). We could
> avoid that dependency if we went by OIDs instead.
Right now you can use a temporary table in place of a system
table using the temporary schema. Would that still work?
test=> BEGIN;
BEGIN
test=> CREATE temporary TABLE pg_class(x INT);
CREATE TABLE
test=> INSERT INTO pg_class VALUES (1);
INSERT 0 1
test=> SELECT * FROM pg_class;
x
---
1
(1 row)
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-04-18 17:38:57 | Re: Problem with PITR recovery |
Previous Message | Tom Lane | 2005-04-18 17:23:26 | Re: Problem with PITR recovery |