From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Clément Prévost <prevostclement(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Documentation on information_ schema columns that does not exist |
Date: | 2016-08-08 01:57:35 |
Message-ID: | e78e3c50-8a0f-56ae-a4ba-c670dc02481b@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 8/3/16 3:27 PM, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2016-08-08 12:20:01 | pg_trgm authors |
Previous Message | Jeff Janes | 2016-08-05 15:53:23 | pg_archivecleanup docs |