Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 26DDE9FB28C for ; Tue, 3 Jul 2007 10:56:59 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 52273-02 for ; Tue, 3 Jul 2007 10:56:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id CCEFE9FB2B9 for ; Tue, 3 Jul 2007 10:56:53 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l63DugOA006928; Tue, 3 Jul 2007 09:56:42 -0400 (EDT) To: Stefan Kaltenbrunner cc: Neil Conway , David Fetter , PostgreSQL Patches , Euler Taveira de Oliveira , Susanne Ebrecht Subject: Re: [DOCS] rename of a view In-reply-to: <4689EECF.9080902@kaltenbrunner.cc> References: <46839C05.7050307@miracee.de> <3450.1183040211@sss.pgh.pa.us> <20070629183219.GO7636@fetter.org> <20070630001653.GQ7636@fetter.org> <4685D8C8.2070808@timbira.com> <12776.1183177571@sss.pgh.pa.us> <1183181585.20942.1.camel@goldbach> <15084.1183181782@sss.pgh.pa.us> <1183182221.20942.8.camel@goldbach> <15362.1183182531@sss.pgh.pa.us> <20070701195528.GX7636@fetter.org> <1183426491.13154.14.camel@dell.linuxdev.us.dell.com> <27614.1183432429@sss.pgh.pa.us> <1183441827.9364.6.camel@goldbach> <4689EECF.9080902@kaltenbrunner.cc> Comments: In-reply-to Stefan Kaltenbrunner message dated "Tue, 03 Jul 2007 08:38:07 +0200" Date: Tue, 03 Jul 2007 09:56:42 -0400 Message-ID: <6927.1183471002@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/48 X-Sequence-Number: 3046 Stefan Kaltenbrunner writes: > Neil Conway wrote: >> On Mon, 2007-02-07 at 23:13 -0400, Tom Lane wrote: >>> Er, was this on the agenda for 8.3? >> >> Well, it seemed fairly harmless to me (no behavioral changes and very >> little new code, just syntax), so I didn't see a compelling reason to >> delay applying it for a few months. But I can revert it if you'd prefer. > hmm so now we have ALTER VIEW/SEQUENCE commands that can do a bit but > not all of what ALTER TABLE can do (renaming columns of a VIEW or > changing the owner for example). > I agree in principle that having those functionality in ALTER > VIEW/SEQUENCE is a good idea but only bringing in a bit of the required > functionality which still does not solve the "uhm why do I need ALTER > TABLE to manipulate a VIEW" months after the feature freeze sounds a bit > wrong to me :-( What's bothering me here is failure to focus. We are not in development mode today, and have not been for months. What we need to be doing is wrapping up the patches that are already on the to-do list, not expending developer effort on new stuff. Neil, according to http://developer.postgresql.org/index.php/Todo:PatchStatus you have accepted two patches to review --- what is happening with those? regards, tom lane