Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Subject: Re: Domains vs data types
From: Florents Tselai <florents.tselai@gmail.com>
In-Reply-To: <CAH2i4yf_M5NfX_kDu6_2Z+sgqLOZK9vCsF3EfmwZQyYFuAMxpg@mail.gmail.com>
Date: Wed, 20 Aug 2025 20:36:52 +0300
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <524E00FE-DBFF-483B-A276-467A0B979B1D@gmail.com>
References: <CAH2i4yf_M5NfX_kDu6_2Z+sgqLOZK9vCsF3EfmwZQyYFuAMxpg@mail.gmail.com>
To: =?utf-8?B?RXJ0YW4gS8O8w6fDvGtvZ2x1?= <ertan.kucukoglu@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/524E00FE-DBFF-483B-A276-467A0B979B1D%40gmail.com>
Precedence: bulk


> On 20 Aug 2025, at 7:47=E2=80=AFAM, Ertan K=C3=BC=C3=A7=C3=BCkoglu =
<ertan.kucukoglu@gmail.com> wrote:
>=20
> Hello,
>=20
> I am using PostgreSQL 17.6.
> I would like to learn if there is any benefit of using domains over =
data types for table column definitions in terms of performance =
gain/loss.
>=20


I know that this doesn=E2=80=99t answer your question, but before =
exploring custom types / domains,
and based on experience, I=E2=80=99d strongly recommend exploring jsonb =
instead as an alternative.

Also note that using custom types can lead to some confusion initially =
for basic stuff=20
you can=E2=80=99t do things like SELECT mytype.f1 and instead you have =
to do (mytype).f1=20
Things like this can get annoying pretty quickly.