MIME-Version: 1.0
References: <CA+FnnTzfvgVdptHcLBFPrq_Q+xPes-Bhjiw_xFiooq4VqhqyrQ@mail.gmail.com>
 <CANzqJaCxZK0j8fL-riZpX+AV+kyo9PcAvgF=H5DgaWK+C+66Vw@mail.gmail.com>
 <CAKFQuwYYgPxUSvo2UzOty5Cd1xw5+2q1bg3+zY-nsXNZyq+_4g@mail.gmail.com> <11AA76D0-CAFE-4A17-BCCF-50520CCDF47F@thebuild.com>
In-Reply-To: <11AA76D0-CAFE-4A17-BCCF-50520CCDF47F@thebuild.com>
From: Igor Korot <ikorot01@gmail.com>
Date: Wed, 8 Jan 2025 13:30:04 -0600
Message-ID: <CA+FnnTxf3VxTPzGFy7q-6ENVcV769F_5_=nbGOvK40qua8XPgg@mail.gmail.com>
Subject: Re: Postgres do not support tinyint?
To: Christophe Pettus <xof@thebuild.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, Ron Johnson <ronljohnsonjr@gmail.com>, 
	"pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BFnnTxf3VxTPzGFy7q-6ENVcV769F_5_%3DnbGOvK40qua8XPgg%40mail.gmail.com>
Precedence: bulk

Hi, Christophe,

On Wed, Jan 8, 2025 at 12:49=E2=80=AFAM Christophe Pettus <xof@thebuild.com=
> wrote:
>
>
>
> > On Jan 7, 2025, at 22:44, David G. Johnston <david.g.johnston@gmail.com=
> wrote:
> >
> > You suggest a type with a minimum size of 6 bytes when the complaint is=
 that the otherwise acceptable 2 byte data type is too large?
>
> Although it's not clear from the OP's question, if there are going to be =
a significant number of these 3-bit fields, packing them into a bitstring m=
ight be a way forward.  It's a good solution for tables with a ton of boole=
ans.

There is no boolean - it is 0-4 inclusive.

Also - there are not too many records in that table...

Thank you.

>