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

Re: BUG #5234: ALTER TABLE ... RENAME COLUMN change view definition incorrectly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Sergey Burladyan <eshkinkot(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5234: ALTER TABLE ... RENAME COLUMN change view definition incorrectly
Date: 2009-12-10 17:32:55
Message-ID: 25344.1260466375@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Dec 10, 2009 at 11:54 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The problem with USING is that it is not merely a join condition but
>> affects the set of columns emitted by the join. It can't be converted
>> to a simple ON without changing the semantics, and I don't believe we
>> should try.

> The OP seemed to be pretty clear on what the semantics should be, and
> I'm not confused either.  Why are you?  :-)

I'm not confused: it's an error condition.  You have not explained why
it isn't.

What would actually be ideal is to throw an error on the attempted column
rename, but I doubt the problem is worth the additions to system
infrastructure that would be necessary to make that happen.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2009-12-10 18:02:43
Subject: Re: BUG #5234: ALTER TABLE ... RENAME COLUMN change view definition incorrectly
Previous:From: Robert HaasDate: 2009-12-10 17:11:10
Subject: Re: BUG #5234: ALTER TABLE ... RENAME COLUMN change view definition incorrectly

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