Horton
Menu

Re: Postgres do not support tinyint?

Christophe Pettus <xof@thebuild.com>

View thread
From: Christophe Pettus <xof@thebuild.com>
To: Igor Korot <ikorot01@gmail.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:34:15Z
Lists: pgsql-general 

> 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. :-)

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.
2. If there are a lot of them, it's worth encoding them into a bitstring.