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

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

On 27.4.2012. 0:39, Tom Lane wrote:
>
> 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
>

Well, there is no supported method for changing order of columns too, but
doesn't stop you from creating new and dropping old until you have
order which you want.

To be exact I didn't clone the database, I let our tool build it.
It built types with different order because our schema changed in the meantime.

Regards,
Rikard

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message petteri.raty 2012-04-27 07:47:50 BUG #6619: Misleading output from slave when host is not running
Previous Message Tom Lane 2012-04-27 02:26:02 Re: log_collector doesn't respond to reloads