Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bV1pF-000848-IQ for pgsql-docs@arkaria.postgresql.org; Wed, 03 Aug 2016 19:27:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bV1pF-0002TZ-1h for pgsql-docs@arkaria.postgresql.org; Wed, 03 Aug 2016 19:27:33 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bV1pD-0002T1-Ts for pgsql-docs@postgresql.org; Wed, 03 Aug 2016 19:27:32 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bV1pB-000062-Dl for pgsql-docs@postgresql.org; Wed, 03 Aug 2016 19:27:30 +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 u73JRRUW015357; Wed, 3 Aug 2016 15:27:27 -0400 From: Tom Lane To: Peter Eisentraut cc: =?UTF-8?B?Q2zDqW1lbnQgUHLDqXZvc3Q=?= , pgsql-docs@postgresql.org Subject: Re: Documentation on information_ schema columns that does not exist In-reply-to: References: <32009.1433109284@sss.pgh.pa.us> <32511.1433110471@sss.pgh.pa.us> Comments: In-reply-to Peter Eisentraut message dated "Wed, 03 Aug 2016 15:05:47 -0400" Date: Wed, 03 Aug 2016 15:27:27 -0400 Message-ID: <15356.1470252447@sss.pgh.pa.us> X-Pg-Spam-Score: -3.1 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org Peter Eisentraut writes: > On 5/31/15 8:27 PM, Clément Prévost wrote: >> Here is another patch to fix the name of the column >> information_schema.routines.result_cast_char_set_name that was >> mistakenly named result_cast_character_set_name. > This one is actually named result_cast_character_set_name in the > standard, although that might be a mistake. Anyway, our documentation > doesn't match our implementation, so one of them has to change. Hm, yeah, I think I vote with the "it's a mistake" camp. The adjacent columns are named "result_cast_char_set_whatever", and there are occurrences of result_cast_char_set_name elsewhere, for example in the method_specifications view. regards, tom lane -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs