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> <CA+FnnTxf3VxTPzGFy7q-6ENVcV769F_5_=nbGOvK40qua8XPgg@mail.gmail.com>
 <051EB6AC-2395-4EAD-B30C-069FBC01107F@thebuild.com>
In-Reply-To: <051EB6AC-2395-4EAD-B30C-069FBC01107F@thebuild.com>
From: Igor Korot <ikorot01@gmail.com>
Date: Wed, 8 Jan 2025 13:40:38 -0600
Message-ID: <CA+FnnTyxnWjjaC4dDo6Y4DeCYAVa3dgGdsMg3sdTOFiyHAG7Ag@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%2BFnnTyxnWjjaC4dDo6Y4DeCYAVa3dgGdsMg3sdTOFiyHAG7Ag%40mail.gmail.com>
Precedence: bulk

Hi, Christopphe,

On Wed, Jan 8, 2025 at 1:34=E2=80=AFPM Christophe Pettus <xof@thebuild.com>=
 wrote:
>
>
>
> > On Jan 8, 2025, at 11:30, Igor Korot <ikorot01@gmail.com> wrote:
> > There is no boolean - it is 0-4 inclusive.
>
> Unless you have somehow gotten PostgreSQL running on an IBM 7070, the ran=
ge 0-4 can be represented by three binary digits, aka booleans. :-)

The only booleans I know of are 0 and 1. ;-)

>
> To be serious, though, the situation is:
>
> 1. If there are just one or two tinyints, having a tinyint type wouldn't =
save any space in the row.

No it is not a lot of them.
So then "smallint" is the best bet, right?

Thank you

> 2. If there are a lot of them, it's worth encoding them into a bitstring.