| From: | Igor Korot <ikorot01(at)gmail(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres do not support tinyint? |
| Date: | 2025-01-08 19:40:38 |
| Message-ID: | CA+FnnTyxnWjjaC4dDo6Y4DeCYAVa3dgGdsMg3sdTOFiyHAG7Ag@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi, Christopphe,
On Wed, Jan 8, 2025 at 1:34 PM Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>
>
> > On Jan 8, 2025, at 11:30, Igor Korot <ikorot01(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-01-08 19:43:33 | Re: INTERVAL MINUTE TO SECOND didn't do what I thought it would do |
| Previous Message | Christophe Pettus | 2025-01-08 19:34:15 | Re: Postgres do not support tinyint? |