Re: BUG #6618: incorrect restore for composite columns when order changes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: rikard(dot)pavelic(at)zg(dot)htnet(dot)hr
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6618: incorrect restore for composite columns when order changes
Date: 2012-04-26 22:39:01
Message-ID: 16145.1335479941@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

rikard(dot)pavelic(at)zg(dot)htnet(dot)hr writes:
> Steps to reproduce problem:
> 1) create composite type
> 2) use composite type as column in a table
> 3) clone database
> 4) change order of attributes in cloned database
> 5) dump to plain sql with column names
> 6) restore sql dump to cloned database

There is no supported method for changing the order of attributes in a
composite type, so I wonder exactly how you did step 4. If it involved
direct manipulation of the system catalogs, I would say this falls in
the category of "if you break it, you get to keep both pieces".

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jaime Casanova 2012-04-26 22:48:31 Re: 291 pg_toast_temp schemas?
Previous Message Josh Berkus 2012-04-26 22:35:17 Re: 291 pg_toast_temp schemas?