From 1657be6863c8d743977d187169603da9e816a471 Mon Sep 17 00:00:00 2001 From: "David G. Johnston" Date: Thu, 9 Jun 2022 16:04:44 +0000 Subject: [PATCH] doc: Move enum storage size to top of section This is done to conform to the location used by other data types. Suggestion by Sumit Sengupta Discussion: https://www.postgresql.org/message-id/BL0PR06MB4978F6C0B69F3F03AEBED0FBB3C29@BL0PR06MB4978.namprd06.prod.outlook.com --- doc/src/sgml/datatype.sgml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 8e30b82273..77e75f09e2 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -3155,6 +3155,13 @@ SELECT * FROM test1 WHERE a; a piece of data. + + An enum value occupies four bytes on disk. 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. + + Declaration of Enumerated Types @@ -3279,13 +3286,6 @@ SELECT person.name, holidays.num_weeks FROM person, holidays values be changed, short of dropping and re-creating the enum type. - - An enum value occupies four bytes on disk. 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. - - The translations from internal enum values to textual labels are kept in the system catalog -- 2.25.1