From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Fujii Masao <fujii(dot)masao(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4109: Typo in documentation |
Date: | 2008-06-23 22:55:18 |
Message-ID: | 200806232255.m5NMtIp26276@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | John | 2008-06-24 03:07:47 | BUG #4260: Cannot even install product |
Previous Message | Bruce Momjian | 2008-06-23 21:11:35 | Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order |