Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1clP3S-0002WU-11 for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Mar 2017 00:02:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1clP3R-00025H-Jy for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Mar 2017 00:02:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1clP3R-000258-5e for pgsql-hackers@postgresql.org; Wed, 08 Mar 2017 00:02:09 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1clP3O-0003ez-DT for pgsql-hackers@postgresql.org; Wed, 08 Mar 2017 00:02:08 +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 v28024Eg011146; Tue, 7 Mar 2017 19:02:04 -0500 From: Tom Lane To: Robert Haas cc: "pgsql-hackers@postgresql.org" Subject: Re: Bizarre choice of case for RELKIND_PARTITIONED_TABLE In-reply-to: References: <27899.1488909319@sss.pgh.pa.us> <8913.1488927818@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Tue, 07 Mar 2017 18:43:10 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11144.1488931324.1@sss.pgh.pa.us> Date: Tue, 07 Mar 2017 19:02:04 -0500 Message-ID: <11145.1488931324@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 Robert Haas writes: > On Tue, Mar 7, 2017 at 6:03 PM, Tom Lane wrote: >> Hm, one would hope that the vast majority of code references are neither >> of those, but rather "RELKIND_PARTITIONED_TABLE". > For reasons which must've seemed good to whoever instituted the > policy, pg_dump refers to relkinds using the bare letters rather than > the constants. Even in pg_dump, it appears to me that the large majority of relkind references use the symbolic names. Quite a few of the violations of that policy look to be new ... and now that I see them, their days are numbered. > (And protocol message types don't even have defined constants. Uggh.) Yeah, that's a different issue, which boils down to the fact that in order to do anything useful we'd need to clutter client-visible namespace with the symbols. I wouldn't be averse to doing something about it as long as it's not done in postgres_ext.h, but if not there where? 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