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.
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>
> Tom Lane ...
In response to
pgsql-bugs by date
|Next:||From: Thomas Kellerer||Date: 2010-02-27 16:28:21|
|Subject: BUG #5348: Postgres crashes with index on xpath_string|
|Previous:||From: Oleg Serov||Date: 2010-02-27 14:16:06|
|Subject: Re: Diffrent column ordering after dump/restore tables with INHERITS|