Horton
Menu

Re: Postgres do not support tinyint?

Igor Korot <ikorot01@gmail.com>

View thread
From: Igor Korot <ikorot01@gmail.com>
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>
Date: 2025-01-08T19:40:38Z
Lists: pgsql-general 
Hi, Christopphe,

On Wed, Jan 8, 2025 at 1:34 PM 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 range 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.