Re: Postgres do not support tinyint? - Mailing list pgsql-general

From Igor Korot
Subject Re: Postgres do not support tinyint?
Date
Msg-id CA+FnnTxf3VxTPzGFy7q-6ENVcV769F_5_=nbGOvK40qua8XPgg@mail.gmail.com
Whole thread Raw
In response to Re: Postgres do not support tinyint?  (Christophe Pettus <xof@thebuild.com>)
Responses Re: Postgres do not support tinyint?
Re: Postgres do not support tinyint?
List pgsql-general
Hi, Christophe,

On Wed, Jan 8, 2025 at 12:49 AM 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
typeis 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,
packingthem into a bitstring might be a way forward.  It's a good solution for tables with a ton of booleans. 

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

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

Thank you.

>



pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: INTERVAL MINUTE TO SECOND didn't do what I thought it would do
Next
From: Christophe Pettus
Date:
Subject: Re: Postgres do not support tinyint?