Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
Subject: Re: Postgres do not support tinyint?
From: Christophe Pettus <xof@thebuild.com>
In-Reply-To: <CAKFQuwYYgPxUSvo2UzOty5Cd1xw5+2q1bg3+zY-nsXNZyq+_4g@mail.gmail.com>
Date: Tue, 7 Jan 2025 22:49:08 -0800
Cc: Ron Johnson <ronljohnsonjr@gmail.com>,
 "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <11AA76D0-CAFE-4A17-BCCF-50520CCDF47F@thebuild.com>
References: <CA+FnnTzfvgVdptHcLBFPrq_Q+xPes-Bhjiw_xFiooq4VqhqyrQ@mail.gmail.com>
 <CANzqJaCxZK0j8fL-riZpX+AV+kyo9PcAvgF=H5DgaWK+C+66Vw@mail.gmail.com>
 <CAKFQuwYYgPxUSvo2UzOty5Cd1xw5+2q1bg3+zY-nsXNZyq+_4g@mail.gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/11AA76D0-CAFE-4A17-BCCF-50520CCDF47F%40thebuild.com>
Precedence: bulk


> On Jan 7, 2025, at 22:44, David G. Johnston =
<david.g.johnston@gmail.com> wrote:
>=20
> 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.=