Re: doc: Move enum storage commentary to top of section - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: doc: Move enum storage commentary to top of section
Date
Msg-id YsjYG5DgMwIO6kjy@momjian.us
Whole thread Raw
In response to Re: doc: Move enum storage commentary to top of section  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: doc: Move enum storage commentary to top of section
List 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@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: doc: Bring mention of unique index forced transaction wait behavior outside of the internal section
Next
From: Bruce Momjian
Date:
Subject: Re: doc: Move enum storage commentary to top of section