| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Arrays vs separate tables |
| Date: | 2025-10-20 14:42:01 |
| Message-ID: | caa70601-f6ee-4dd7-9259-7ab9ecc5497b@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 the manner you want then
don't change things. Given the size of your datasets I don't see that
changes will materially affect the performance of your queries. I am
pretty sure most of the time the Postgres planner is resorting to a
sequence scan anyway.
>
> Rich
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2025-10-20 14:48:10 | Re: Arrays vs separate tables |
| Previous Message | Rich Shepard | 2025-10-20 14:32:22 | Re: Arrays vs separate tables |