Re: Resurrecting pg_upgrade - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Resurrecting pg_upgrade
Date
Msg-id 20031215025123.GA14029@dcc.uchile.cl
Whole thread Raw
In response to Re: Resurrecting pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Resurrecting pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Dec 14, 2003 at 09:48:20PM -0500, Tom Lane wrote:
> Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> > What about cached OIDs in view and function definitions, etc...?
> 
> Doesn't matter.  Catalog entries are dumped and reloaded; there is no
> carry-forward of OIDs.
> 
> I suppose if someone were storing OIDs of tables or functions or views
> in user tables, this procedure would break the references.  But that
> would be true of a dump/reload under current procedures as well.  I'm
> willing to say that that's unsupported.

Large objects included?

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
FOO MANE PADME HUM


pgsql-hackers by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: ORDER BY and DISTINCT ON
Next
From: Tom Lane
Date:
Subject: Re: ORDER BY and DISTINCT ON