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

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

From: Oleg Serov <serovov(at)gmail(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Diffrent column ordering after dump/restore tables with INHERITS
Date: 2010-02-26 18:22:27
Message-ID: cec7c6df1002261022g41304f71m3f570a2cc1456533@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
So there are no simple way to do it right, and it will be not fixed? Will
this bug appear in todo list?

On Fri, Feb 26, 2010 at 6:13 PM, Greg Stark <gsstark(at)mit(dot)edu> wrote:

> 2010/2/26 Oleg Serov <serovov(at)gmail(dot)com>:
> > Up! Anybody will answer about the patch?
>
> The patch causes the inheritance history to be lost. If you
> subsequently drop the column form the parent it'll be kept on the
> child because it was explicitly declared when you created the child.
> In the original structure if you dropped the column from the parent it
> would be dropped from the child because it was an inherited column.
>
> Inheritance is in a kind of no-mans land. It's not good enough to be
> an important feature anyone cares enough about to make it work
> properly and it's not shoddy enough that it's worth removing. I'm sure
> there are people using it effectively despite the caveats and rough
> edges.
>
> --
> greg
>



-- 
С уважением

Олег Серов

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2010-02-26 18:29:54
Subject: Re: Diffrent column ordering after dump/restore tables with INHERITS
Previous:From: Tom LaneDate: 2010-02-26 16:55:12
Subject: Re: BUG #5347: initdb does not work when a data directory has been deleted

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