Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sPSad-004ij5-5t for pgsql-general@arkaria.postgresql.org; Thu, 04 Jul 2024 19:57:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sPSZc-002XP5-KP for pgsql-general@arkaria.postgresql.org; Thu, 04 Jul 2024 19:56:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sPSZc-002XOx-9N for pgsql-general@lists.postgresql.org; Thu, 04 Jul 2024 19:56:56 +0000 Received: from mail-oi1-x22a.google.com ([2607:f8b0:4864:20::22a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sPSZa-000RNx-Px for pgsql-general@lists.postgresql.org; Thu, 04 Jul 2024 19:56:56 +0000 Received: by mail-oi1-x22a.google.com with SMTP id 5614622812f47-3d55e2e0327so502934b6e.0 for ; Thu, 04 Jul 2024 12:56:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720123012; x=1720727812; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hH2iv0mAjOOulM8ns44aRi/swKlb+2x2LZPlhUY/fKM=; b=Ta12Jwgr4v410ySzHlDgMpyo0KTwpCPmm/Qa7EYdvdFnjZkIW2RoU8CFTNDEjQsle7 bQSrdMSBTqNKuKW4nQzy7/7YuYbLO7rHXpDSyBA/i2gOIJIQBs4bFbFmQuw8CGGuu71U qIPFWoApDraPLirfhqEw4gCRC6VD/vBcP7B1xEwaHMXPla4FptEAeOOgUVUEe2h36/8q yEjuZOjOQsIiqXSiXeig4ZCTOYBJb18OCKqakSOA4V4oIbgoutipL5SztM8vLRK6fxS+ HBJdcY82VjDE6yDiKjDil49vlmT/j7aGIozeTIbV3vIULsEq91O/cvjWlKbumMXxHy3h cCmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720123012; x=1720727812; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=hH2iv0mAjOOulM8ns44aRi/swKlb+2x2LZPlhUY/fKM=; b=EFS1PQhxuzztZAMofCsCW25h3uiQn1tuK+3JNjFcf5ieg7Vgui3wADE2VBWCV7vwDL 60FYA/dmW/scFke0GPghgWzWF4ZWwAA6x28kdzgpwaNPUmOLiA5tLhJkkZazn1o9I4S6 grYjjoWmbcI+MQiVicyDaroWwC/w7qO0c+vOVJ5QLV1pLQqeqXadwSEVM1H6ML7j/ntx IKjZJNmzXpBexoKXoeK4sfHnmvT/jM7+tjXoSsRqRz2kCJDjlL+xvdw5806AmPT8nJTM yS2bgXYXiIlResIdZEmiJMYYcZDmEgJFLVZra3A7FYV/VxHR1Q7EiX5ybVweYOel4rr8 6yHQ== X-Gm-Message-State: AOJu0YyIlitcu3uOXlRFpnjJJfnxIJSNVJUkwQ+CEAaQ6D4R9TN1mg5e wiK+AlJpSIKKyfuzqh8XGfZy15ex625SuUNiG+KLxrFhFXs8lJmfqkFXcrAap5tqyKweM4KdBdz MaTqCxfeGXNUm1ktdTJf2Pfi4S/KYtw== X-Google-Smtp-Source: AGHT+IFLnmyvDIh7+44xvzCcLfnbhhEnVklMztzUkfgUtAjG8mFyrFLoKXN32JMUC7tOlXAAduSa01M+28bUCRXKaXw= X-Received: by 2002:a05:6870:4410:b0:254:b24e:e351 with SMTP id 586e51a60fabf-25e2bf96668mr2050714fac.59.1720123012349; Thu, 04 Jul 2024 12:56:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Thu, 4 Jul 2024 12:56:14 -0700 Message-ID: Subject: Re: Design strategy for table with many attributes To: Lok P Cc: pgsql-general Content-Type: multipart/alternative; boundary="0000000000001f05e7061c7159fb" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001f05e7061c7159fb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jul 4, 2024 at 12:38=E2=80=AFPM Lok P 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 fetc= h > 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. --0000000000001f05e7061c7159fb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Jul 4, 2024 at 12:38=E2=80=AFPM Lok P <loknath.73@gmail.com> wrote:=

Should we break the singl= e transaction into multiple tables like one main table and other addenda ta= bles with the same primary key to join and fetch the results wherever neces= sary?


I would say ye= s.=C2=A0 Find a way to logically group sets of columns together and place t= hose groups into separate tables.=C2=A0 I'd also be looking for cases w= here multiple columns really should be multiple rows.=C2=A0 This is not unc= ommon.

David J.


Davi= d J.
--0000000000001f05e7061c7159fb--