Re: BUG #4109: Typo in documentation - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #4109: Typo in documentation
Date
Msg-id 200806232255.m5NMtIp26276@momjian.us
Whole thread Raw
In response to Re: BUG #4109: Typo in documentation  (Fujii Masao <fujii.masao@oss.ntt.co.jp>)
List pgsql-bugs
Fujii Masao wrote:
> Heikki Linnakangas wrote:
> >> I found the typo in
> >> http://www.postgresql.org/docs/8.3/static/datatype-enum.html .
> >>
> >>> The length of an enum value's textual label is limited by the NAMEDATALEN
> >>> setting compiled into PostgreSQL; in standard builds this means at most 63
> >> bytes.
> >>
> >> Correct is that the NAMEDATALEN means 64 bytes in standard builds.
> >
> > No. NAMEDATALEN is 64 bytes, but the 64th byte is reserved for the
> > null-terminator, so the string stored can be at most 63 bytes long.
>
> Ok.
>
> But, it's described that NAMEDATALEN is 64 bytes in
> http://www.postgresql.org/docs/8.3/static/sql-createtype.html.
>
> This conflict can confuse the user. So, should we unite the
> descriptions of the number of bytes for NAMEDATALEN?

The create_type.sgml file says:

    must be _less_ _than_ <symbol>NAMEDATALEN</symbol> bytes long

so it seems consistent to me.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order
Next
From: "John"
Date:
Subject: BUG #4260: Cannot even install product