Re: Arrays vs separate tables - Mailing list pgsql-general

From Rob Sargent
Subject Re: Arrays vs separate tables
Date
Msg-id D2D4C174-736D-4D1C-8A9A-9E692D8088EA@gmail.com
Whole thread Raw
In response to Re: Arrays vs separate tables  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general

> On Oct 20, 2025, at 8:42 AM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>
> On 10/20/25 07:07, Rich Shepard wrote:
>>> On Mon, 20 Oct 2025, Michał Kłeczek wrote:
>>> There is also another concern - do you want to make sure phone numbers are
>>> not shared?
>> Michal,
>> Shared with whom? I run a solo professional services consultancy so there's
>> only me here the database.
>
> That is the heart of the matter, you should do what makes sense to you. If you can get the information you need in
themanner you want then don't change things. Given the size of your datasets I don't see that changes will materially
affectthe performance of your queries. I am pretty sure most of the time the Postgres planner is resorting to a
sequencescan anyway. 

And all the hot tables have been paged in if not the entire db.


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Arrays vs separate tables
Next
From: Michał Kłeczek
Date:
Subject: Re: Arrays vs separate tables