Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YU7KU-0006Rt-Ro for pgsql-hackers@arkaria.postgresql.org; Sat, 07 Mar 2015 05:31:14 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YU7KU-0005rC-Bd for pgsql-hackers@arkaria.postgresql.org; Sat, 07 Mar 2015 05:31:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YU7KT-0005r4-DS for pgsql-hackers@postgresql.org; Sat, 07 Mar 2015 05:31:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YU7KQ-0004cO-68 for pgsql-hackers@postgresql.org; Sat, 07 Mar 2015 05:31:12 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t275V38l004594; Sat, 7 Mar 2015 00:31:03 -0500 From: Tom Lane To: Peter Eisentraut cc: Adam Brightwell , Noah Misch , Stephen Frost , PostgreSQL Hackers Subject: Re: CATUPDATE confusion? In-reply-to: <54FA8203.8080709@gmx.net> References: <20141227080926.GA2035611@tornado.leadboat.com> <20141227151034.GU3062@tamriel.snowman.net> <28382.1419703324@sss.pgh.pa.us> <20141227231829.GX3062@tamriel.snowman.net> <1952.1419722762@sss.pgh.pa.us> <20141227233150.GA2046947@tornado.leadboat.com> <54FA8203.8080709@gmx.net> Comments: In-reply-to Peter Eisentraut message dated "Fri, 06 Mar 2015 23:43:47 -0500" Date: Sat, 07 Mar 2015 00:31:03 -0500 Message-ID: <4593.1425706263@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Peter Eisentraut writes: > On 12/29/14 7:16 PM, Adam Brightwell wrote: >> Given this discussion, I have attached a patch that removes CATUPDATE >> for review/discussion. > committed this version Hmm .. I'm not sure that summarily removing usecatupd from those three system views was well thought out. pg_shadow, especially, has no reason to live at all except for backwards compatibility, and clients might well expect that column to still be there. I wonder if we'd not be better off to keep the column in the views but have it read from rolsuper. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers