> On Jan 7, 2025, at 22:44, David G. Johnston <david.g.johns...@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 might be a way forward. It's a good solution for tables with a ton of booleans.
- Postgres do not support tinyint? Igor Korot
- Re: Postgres do not support tinyint? Adrian Klaver
- Re: Postgres do not support tinyint? Ron Johnson
- Re: Postgres do not support tinyint? Igor Korot
- Re: Postgres do not support tinyint? Christophe Pettus
- Re: Postgres do not support tinyint? David G. Johnston
- Re: Postgres do not support tinyint? Christophe Pettus
- Re: Postgres do not support tinyint? Igor Korot
- Re: Postgres do not support tinyi... Christophe Pettus
- Re: Postgres do not support t... Igor Korot
- Re: Postgres do not suppo... Vladlen Popolitov
- Re: Postgres do not suppo... Dominique Devienne
- Re: Postgres do not suppo... shammat
- Re: Postgres do not suppo... Vladlen Popolitov
- Re: Postgres do not support tinyi... Alvaro Herrera
- Re: Postgres do not support tinyint? Tom Lane