Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Subject: Re: Arrays vs separate tables
From: =?utf-8?Q?Micha=C5=82_K=C5=82eczek?= <michal@kleczek.org>
In-Reply-To: <95de5a9b-4dd8-2f7-6e12-98c3d72c52@appl-ecosys.com>
Date: Mon, 20 Oct 2025 15:38:21 +0200
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC75487C-BBDF-474D-880A-87FB6CEED812@kleczek.org>
References: <162e5330-861c-ecc7-45c1-aaa1aff26c88@appl-ecosys.com>
 <pyh2kcisxwrhzz255gaiaawo5yubirdifzsfvz3okqcjeaaqqr@6lq5n6idswg7>
 <95de5a9b-4dd8-2f7-6e12-98c3d72c52@appl-ecosys.com>
To: Rich Shepard <rshepard@appl-ecosys.com>
Archived-At: <https://www.postgresql.org/message-id/CC75487C-BBDF-474D-880A-87FB6CEED812%40kleczek.org>
Precedence: bulk


> On 20 Oct 2025, at 14:55, Rich Shepard <rshepard@appl-ecosys.com> =
wrote:
>=20
> On Mon, 20 Oct 2025, Peter J. Holzer wrote:
>=20
>> * Simplicity: If a set of values is always fetched together and =
updated
>> together, you might as well treat it as a unit and not split it over
>> multiple tables
>=20
>> The second may be relevant for you. If you always display and edit =
the
>> phone numbers of a contact together and your frontend makes it easier =
to
>> edit an array than a subset of rows from a table, you might just =
stuff
>> them into a table and ignore "purity".
>=20
> Peter,
>=20
> Thank you. That's my use case.

There is also another concern - do you want to make sure phone numbers =
are not shared?

=E2=80=94
Michal=