Re: Assigning fixed OIDs to system catalogs and indexes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: 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-13 02:13:25
Message-ID: 2011.1113358405@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-04-13 02:28:03 Re: Assigning fixed OIDs to system catalogs and indexes
Previous Message Alvaro Herrera 2005-04-13 02:10:43 Re: Assigning fixed OIDs to system catalogs and indexes