Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables
Date
Msg-id b42b73150912020823iace69w4337005d1b18b3fd@mail.gmail.com
Whole thread Raw
In response to Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables
Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables
List pgsql-hackers
On Thu, Aug 6, 2009 at 9:28 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> The half-formed idea I had was a set of GUC variables:
>
> set next_pg_class_oid = 12345;
> set next_pg_type_oid = 12346;
> set next_toast_table_oid = ...
> set next_toast_index_oid = ...
>
> and finally it could do CREATE TABLE.  CREATE TYPE would only need
> next_pg_type_oid (except for a composite type).

Is this idea still on the table for 8.5?

merlin


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Adding support for SE-Linux security
Next
From: Tom Lane
Date:
Subject: Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables