Re: Removing pg_migrator limitations - Mailing list pgsql-hackers

From Joe Conway
Subject Re: Removing pg_migrator limitations
Date
Msg-id 4B2C2BEA.4000603@joeconway.com
Whole thread Raw
In response to Re: Removing pg_migrator limitations  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Removing pg_migrator limitations
List pgsql-hackers
On 12/18/2009 04:09 PM, Tom Lane wrote:
> At the moment it appears that we need the following hacks:
>
> * ability to control the OIDs assigned to user tables and types.
> Because a table also has a rowtype, this means at least two separate
> state variables.  And we already knew we had to control the OIDs
> assigned to toast tables.  I'm imagining dump output like
>
>     select pg_migrator_set_next_table_oid(123456);
>     select pg_migrator_set_next_type_oid(12347);
>     select pg_migrator_set_next_toast_table_oid(123458);
>
>     CREATE TABLE ...

I like this approach overall, but wonder if it would be better to do:
select pg_migrator_set_next_oid('table', 123456);select pg_migrator_set_next_oid('type', 12347);select
pg_migrator_set_next_oid('toast_table',123458); 

etc. Later we could easily add other supported objects...


Joe


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Removing pg_migrator limitations
Next
From: Tom Lane
Date:
Subject: Re: Removing pg_migrator limitations