Skip site navigation (1) Skip section navigation (2)

Re: Diffrent column ordering after dump/restore tables with INHERITS

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Oleg Serov <serovov(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>
Subject: Re: Diffrent column ordering after dump/restore tables with INHERITS
Date: 2010-02-27 16:02:08
Message-ID: 407d949e1002270802m208c0b3cw80ab8b57da7583a6@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
yes, that's on the todo list.you can search back in the archives for
discussions on how to do this without making the code difficult to debug.

this is a bug but it's a longstanding  known bug inan area where we have
lots of known limitations and nobody is too excited about spending lots of
effort to fix up.

greg

On 27 Feb 2010 14:16, "Oleg Serov" <serovov(at)gmail(dot)com> wrote:

I'm think you should add some abstract-layer for handling column ordering
not as they stored at disk. It is possible?



On Fri, Feb 26, 2010 at 10:32 PM, Alvaro Herrera <alvherre(at)commandprompt(dot)com>
wrote:
>
> Tom Lane ...
-- 
С уважением

Олег Серов

In response to

pgsql-bugs by date

Next:From: Thomas KellererDate: 2010-02-27 16:28:21
Subject: BUG #5348: Postgres crashes with index on xpath_string
Previous:From: Oleg SerovDate: 2010-02-27 14:16:06
Subject: Re: Diffrent column ordering after dump/restore tables with INHERITS

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group