Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bV1UH-00078B-JL for pgsql-docs@arkaria.postgresql.org; Wed, 03 Aug 2016 19:05:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bV1UH-0002Et-5r for pgsql-docs@arkaria.postgresql.org; Wed, 03 Aug 2016 19:05:53 +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 1bV1UG-0002DC-9c for pgsql-docs@postgresql.org; Wed, 03 Aug 2016 19:05:52 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bV1UD-0001no-9D for pgsql-docs@postgresql.org; Wed, 03 Aug 2016 19:05:51 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id CFFB620747; Wed, 3 Aug 2016 15:05:47 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Wed, 03 Aug 2016 15:05:47 -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=zQP8FM5p/0ga5iF GrJX/6ctPdQU=; b=iyRLVt3BLeSg3CN5jo9gYlkNbuIwUVwTa68YLd+9CxAtGYL /fuwwlJ9IUrFOYcPoYgVjBpfkitTNtTsHkyOf9DsDAbmWUAC2rVEgA4k1BW5C88u TnKgXpTOyLC4LUn5KZ5XJmBn77dUGXGTT4bM6LmSarDT0KGeF2ajkIWtNJxs= X-Sasl-enc: ZtrsH2jvgXl6St4BBcDm6W3NHRtymuwz68bZxZKXpc5Q 1470251147 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 8F1C9F2D29; Wed, 3 Aug 2016 15:05:47 -0400 (EDT) Subject: Re: Documentation on information_ schema columns that does not exist To: =?UTF-8?B?Q2zDqW1lbnQgUHLDqXZvc3Q=?= , Tom Lane References: <32009.1433109284@sss.pgh.pa.us> <32511.1433110471@sss.pgh.pa.us> Cc: pgsql-docs@postgresql.org From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 3 Aug 2016 15:05:47 -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: Content-Type: text/plain; charset=utf-8 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 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. -- 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