> On Jan 8, 2025, at 11:30, Igor Korot <ikoro...@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.
- 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