| 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:30:04 |
| Message-ID: | CA+FnnTxf3VxTPzGFy7q-6ENVcV769F_5_=nbGOvK40qua8XPgg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi, Christophe,
On Wed, Jan 8, 2025 at 12:49 AM Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>
>
> > On Jan 7, 2025, at 22:44, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)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.
There is no boolean - it is 0-4 inclusive.
Also - there are not too many records in that table...
Thank you.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2025-01-08 19:34:15 | Re: Postgres do not support tinyint? |
| Previous Message | Ron Johnson | 2025-01-08 19:00:00 | INTERVAL MINUTE TO SECOND didn't do what I thought it would do |