| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: doc: Move enum storage commentary to top of section |
| Date: | 2022-07-09 01:21:31 |
| Message-ID: | YsjYG5DgMwIO6kjy@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 6, 2022 at 10:34:58AM -0700, David G. Johnston wrote:
> Agreed.
>
> Tangentially: It does seem a bit unusual to call the fact that the values both
> case-sensitive and limited to the length of a system identifier an
> implementation detail. But if anything the length is more of one than the
> case-sensitivity. Specifying NAMEDATALEN here seems like it breaks
> encapsulation, it could refer by comparison to an identifier and only those
> that care can learn how that length might be changed in a custom build of
> PostgreSQL.
I don't think we can do much to improve what we have already in the
docs.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-07-09 01:21:55 | Re: doc: Move enum storage commentary to top of section |
| Previous Message | Bruce Momjian | 2022-07-09 01:11:43 | Re: doc: Bring mention of unique index forced transaction wait behavior outside of the internal section |