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

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

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, 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, 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-24 18:45:33
Message-ID: 9C5FB2B2F33F8E24813C5146@amenophis (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

--On 24. Januar 2010 13:23:14 -0500 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I think my concern about the original proposal was that the time to
> perform an ALTER RENAME would increase with the number of tables in the
> database, even if they were entirely unrelated to the one you're trying
> to rename.

Uhm, find_column_origin() scans pg_inherits recursively by looking up 
inhparent from the given inhrelid. I don't see where this should be related 
to the number of tables not part of the inheritance tree (or inheritance at 



In response to


pgsql-hackers by date

Next:From: Euler Taveira de OliveiraDate: 2010-01-24 18:50:34
Subject: Re: Resetting a single statistics counter
Previous:From: Pavel StehuleDate: 2010-01-24 18:45:00
Subject: Re: Review: listagg aggregate

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