Re: Design strategy for table with many attributes

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Lok P <loknath(dot)73(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Design strategy for table with many attributes
Date: 2024-07-04 19:56:14
Message-ID: CAKFQuwYpai5snt5mEgyXK4m6nR5T6sP-YTYH-GQ0Hs2rXS7uLA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jul 4, 2024 at 12:38 PM Lok P <loknath(dot)73(at)gmail(dot)com> wrote:

>
> Should we break the single transaction into multiple tables like one main
> table and other addenda tables with the same primary key to join and fetch
> the results wherever necessary?
>
>
I would say yes. Find a way to logically group sets of columns together
and place those groups into separate tables. I'd also be looking for cases
where multiple columns really should be multiple rows. This is not
uncommon.

David J.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2024-07-04 20:06:45 Re: Configure autovacuum
Previous Message Lok P 2024-07-04 19:37:47 Design strategy for table with many attributes