Re: Design strategy for table with many attributes - Mailing list pgsql-general

From David G. Johnston
Subject Re: Design strategy for table with many attributes
Date
Msg-id CAKFQuwYpai5snt5mEgyXK4m6nR5T6sP-YTYH-GQ0Hs2rXS7uLA@mail.gmail.com
Whole thread Raw
In response to Design strategy for table with many attributes  (Lok P <loknath.73@gmail.com>)
Responses Re: Design strategy for table with many attributes
List pgsql-general
On Thu, Jul 4, 2024 at 12:38 PM Lok P <loknath.73@gmail.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.

pgsql-general by date:

Previous
From: Lok P
Date:
Subject: Design strategy for table with many attributes
Next
From: Adrian Klaver
Date:
Subject: Re: Configure autovacuum