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

Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Thom Brown <thombrown(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Subject: Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns
Date: 2010-01-03 19:06:04
Message-ID: 99BC948C-0750-40B5-B2DA-8F07D850D04B@gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Jan 3, 2010, at 12:31 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> In practice the reasonable engineering alternatives may just be to do
> what KaiGai's patch does, or to do nothing.  In that case I think a  
> good
> argument can be made for the latter.  Nobody has ever complained about
> this from the field AFAIR; but we might get complaints if we disable
> cases that used to work fine.

Maybe. The current behavior of allowing the rename but then breaking  
queries certainly isn't awesome.  I think  if someone is willing to  
implement a more careful check we should accept it.

...Robert

In response to

Responses

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2010-01-03 19:13:28
Subject: Re: win32 socket definition
Previous:From: David E. WheelerDate: 2010-01-03 18:53:34
Subject: Re: Testing with concurrent sessions

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