Re: Postgres do not support tinyint?
Igor Korot <ikorot01@gmail.com>
From: Igor Korot <ikorot01@gmail.com>
To: Christophe Pettus <xof@thebuild.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>,
Ron Johnson <ronljohnsonjr@gmail.com>, "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2025-01-08T19:30:04Z
Lists: 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 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. >