| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(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:49:23 |
| Message-ID: | 24117.1113846563@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> 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?
Sure. This doesn't change any externally visible behavior ... other
than the response to unsupported changes to the system catalogs ;-)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-04-18 17:49:25 | Re: Problem with PITR recovery |
| Previous Message | Bruce Momjian | 2005-04-18 17:41:16 | Re: Problem with PITR recovery |