Re: Resurrecting pg_upgrade - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Resurrecting pg_upgrade
Date
Msg-id 3FDD1F6E.5030100@familyhealth.com.au
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
> No.  The proposed pg_upgrade procedure doesn't try to reproduce OIDs of
> catalog entries (other than toast-table OIDs, which are never
> preassigned anyway), so there's no issue.
> 
> Good point though --- thanks for thinking about it.

What about cached OIDs in view and function definitions, etc...?

Like if someone had a view that used the old oidrand() function and now 
we reused that oid for a new, completely different function, would 
breakage occur?

Chris



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Resurrecting pg_upgrade
Next
From: Neil Conway
Date:
Subject: Re: ORDER BY and DISTINCT ON