Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bWZoy-0005Kj-W6 for pgsql-docs@arkaria.postgresql.org; Mon, 08 Aug 2016 01:57:41 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bWZoy-0007xw-J0 for pgsql-docs@arkaria.postgresql.org; Mon, 08 Aug 2016 01:57:40 +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 1bWZoy-0007xo-6P for pgsql-docs@postgresql.org; Mon, 08 Aug 2016 01:57:40 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bWZov-0003YJ-AN for pgsql-docs@postgresql.org; Mon, 08 Aug 2016 01:57:39 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 7B59520294; Sun, 7 Aug 2016 21:57:36 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Sun, 07 Aug 2016 21:57:36 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=R72rQxswRx2iqpL RdUxqv26fIds=; b=KTy9JWry7ADp/S8xdcYgA5xOXJMn6zUtJqje31+Y281xQeL cmdihVCRyQxwqpQE28+Gcztt9xGvAy4SiotlKrpxOc0X4g7YaQ1A1BYlTFpqsFdn xaNiN1maxGmVokJG7lAWFt2F7QQVNcbYhZOxpCAhXzvQx6fxihgY2NNA/bnE= X-Sasl-enc: w5PzXRHbEpqzHj9pFaEalaGBv0PtaK6nYAvdGkVb+Jkj 1470621456 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 21442F2970; Sun, 7 Aug 2016 21:57:36 -0400 (EDT) Subject: Re: Documentation on information_ schema columns that does not exist To: Tom Lane References: <32009.1433109284@sss.pgh.pa.us> <32511.1433110471@sss.pgh.pa.us> <15356.1470252447@sss.pgh.pa.us> Cc: =?UTF-8?B?Q2zDqW1lbnQgUHLDqXZvc3Q=?= , pgsql-docs@postgresql.org From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Sun, 7 Aug 2016 21:57:35 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <15356.1470252447@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.6 (--) 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 On 8/3/16 3:27 PM, Tom Lane wrote: > 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. Fixed by changing the column name. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs