Re: [PATCH] document pg_encoding_to_char() and pg_char_to_encoding() - Mailing list pgsql-hackers

From Ian Lawrence Barwick
Subject Re: [PATCH] document pg_encoding_to_char() and pg_char_to_encoding()
Date
Msg-id CAB8KJ=jB=T24Jnptz3LkP6uaoTMEAj1K+Th9mq75r90T8Xtfsw@mail.gmail.com
Whole thread Raw
In response to [PATCH] document  (Ian Lawrence Barwick <barwick@gmail.com>)
List pgsql-hackers
2021年7月14日(水) 14:43 Ian Lawrence Barwick <barwick@gmail.com>:
>
> Hi
>
> The description for "pg_database" [1] mentions the function
> "pg_encoding_to_char()", but this is not described anywhere in the docs. Given
> that that it (and the corresponding "pg_char_to_encoding()") have been around
> since 7.0 [2], it's probably not a burning issue, but it seems not entirely
> unreasonable to add short descriptions for both (and link from "pg_conversion"
> while we're at it); see attached patch. "System Catalog Information Functions"
> seems the most logical place to put these.
>
> [1] https://www.postgresql.org/docs/current/catalog-pg-database.html
> [2] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=5eb1d0deb15f2b7cd0051bef12f3e091516c723b
>
> Will add to the next commitfest.

Added; apologies, the subject line of the original mail was
unintentionally truncated.

Regards

Ian Barwick

--
EnterpriseDB: https://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Remove repeated calls to PQserverVersion
Next
From: Masahiko Sawada
Date:
Subject: Re: Transactions involving multiple postgres foreign servers, take 2