Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nmadN-0007Ra-4t for pgsql-docs@arkaria.postgresql.org; Thu, 05 May 2022 12:31:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nmadM-0001eg-0w for pgsql-docs@arkaria.postgresql.org; Thu, 05 May 2022 12:31:04 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nmadL-0001eX-OB for pgsql-docs@lists.postgresql.org; Thu, 05 May 2022 12:31:03 +0000 Received: from mail-ed1-x52e.google.com ([2a00:1450:4864:20::52e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nmadJ-0006kj-8n for pgsql-docs@lists.postgresql.org; Thu, 05 May 2022 12:31:02 +0000 Received: by mail-ed1-x52e.google.com with SMTP id t5so5001725edw.11 for ; Thu, 05 May 2022 05:31:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=aJrttFfRxYWS0ERATkn7KTR8KlrPUaOl0PCeMGjBdLM=; b=XJL5OTcxdsO69e7IHyryfu7VQYEtfIYQdcH3L+hkCDgs48fJH74wvZ66V81a1BG9Ij MHmBxciBqLDjjqxZPaPRZ7DO/lUX1wrPqkDEN0RN1UivNmn4SpHTycdj7Wmc51w53nYW v701yZNi+W62Zp8rZkIjUcktC8Auy14YFN+bSfnodDRAkginTP5ETgKkR9ukY9D+awft GqTIo9aOTqLzHIPiScGWbFHhUklDEVJeN3uQGhk6YAI7szDpoWreHrXcS2t2a1kSiwMS +hxTEVz95edQUIb7zHWR6HifPyYOrfXomYYhSb09zyq+TIQwz/US5yeEP5KjjuOuVajr 0+3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=aJrttFfRxYWS0ERATkn7KTR8KlrPUaOl0PCeMGjBdLM=; b=wIH/mxtUSo+w7bvKAr2yM62CGYO7x0vfFMWUvWH639bUr5RRIMFQinkhB11HUJBhaN X28YrjKS8C+GNp86Y7U7RU0BM4eKnN+kWP6tDCurYUtYZmUlWXImdrissIPy1Eahsmv+ Idyrx0nZ6aiqHRUGYnf+/z5D+cT3xxnDSyE++Fxl5aBiuYdFdbWds7JCvCNDugCIF8Fo IiOlIE8mewtekQGX3Dsjfx3/JqmOp41d7o/EdW3KoclWK37X//TKnQ72pN0xs8OdYrhh T6LTVm5QZdyXD6h9wQZye1UenKE1WboXL9egiNTCHHliECost4TYQ7kJhpBmOksVDw/k 3DEA== X-Gm-Message-State: AOAM533rOxtQCb37kXsNSZmuZWxGYKOAV42gqnqENsacUMInUfaFNSZA 07BS8oaF138EGLf5vyc+mvrJsdpjpfBu80hPFmI= X-Google-Smtp-Source: ABdhPJzz74Kjb143NposFdQzr4VJU6mYbop0wd4chEkqwerAhLo/3G+NgQ5Q3AT0rDWDYSqvwZLOWk1FASfy1G20VNs= X-Received: by 2002:a05:6402:3508:b0:427:b100:b825 with SMTP id b8-20020a056402350800b00427b100b825mr26424063edd.268.1651753859141; Thu, 05 May 2022 05:30:59 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:640c:2bc8:b0:15b:bd92:6856 with HTTP; Thu, 5 May 2022 05:30:58 -0700 (PDT) In-Reply-To: <165169921944.683.8982699018922635049@wrigleys.postgresql.org> References: <165169921944.683.8982699018922635049@wrigleys.postgresql.org> From: "David G. Johnston" Date: Thu, 5 May 2022 05:30:58 -0700 Message-ID: Subject: Re: Specify bytes storage for enum data types To: "ssengupta@hotmail.com" , "pgsql-docs@lists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000007d51e05de42ea2f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000007d51e05de42ea2f Content-Type: text/plain; charset="UTF-8" On Wednesday, May 4, 2022, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/datatype-enum.html > Description: > > I love Postgres !! And also its documentation !! > > While reading through data types, it occurred to me that most ( if not > every > ) other data types has a chart on the top saying how many bytes it > occuies. > Like all numerical, date or char data types. > > For enum it would be nice to have that info as well. > I am assuming it is variable ? May be 1 or 2 bytes for the definition and > the rest depending on the enum values ? > > A clarification would be nice ! > Second to last sentence on the page. Storage only measures the size of a single value on a data row. David J. --00000000000007d51e05de42ea2f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Wednesday, May 4, 2022, PG Doc comments form <noreply@postgresql.org> wrote:
The following documentation comment has been logged= on the website:

Page: https://www.postgresql.org/docs/14/datatype-enum.html
Description:

I love Postgres !! And also its documentation !!

While reading through data types, it occurred to me that most ( if not ever= y
) other data types has a chart on the top saying how many bytes it
occuies.
Like all numerical, date or char data types.

For enum it would be nice to have that info as well.
I am assuming it is variable ? May be 1 or 2 bytes for the definition and the rest depending on the enum values ?

A clarification would be nice !

Second to last sentence on the page.
=

Storage only measures the size of a single value on a d= ata row.

David J.=C2=A0
--00000000000007d51e05de42ea2f--