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

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: Diffrent column ordering after dump/restore tables with INHERITS
Дата
Msg-id 407d949e1002270802m208c0b3cw80ab8b57da7583a6@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Diffrent column ordering after dump/restore tables with INHERITS  (Oleg Serov <serovov@gmail.com>)
Список 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@gmail.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@commandprompt.co=
m>
wrote:
>
> Tom Lane ...
--=20
=F3 =D5=D7=C1=D6=C5=CE=C9=C5=CD

=EF=CC=C5=C7 =F3=C5=D2=CF=D7

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Raphael Palestino Serpa
Дата:
Сообщение:
Следующее
От: "Thomas Kellerer"
Дата:
Сообщение: BUG #5348: Postgres crashes with index on xpath_string