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 1tPmsK-00FILC-Oj for pgsql-general@arkaria.postgresql.org; Mon, 23 Dec 2024 18:09:53 +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 1tPmsK-00DzU4-5i for pgsql-general@arkaria.postgresql.org; Mon, 23 Dec 2024 18:09:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tPmsJ-00DzTv-JS for pgsql-general@lists.postgresql.org; Mon, 23 Dec 2024 18:09:51 +0000 Received: from mail-oi1-x22f.google.com ([2607:f8b0:4864:20::22f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tPmsI-000DbJ-0A for pgsql-general@postgresql.org; Mon, 23 Dec 2024 18:09:50 +0000 Received: by mail-oi1-x22f.google.com with SMTP id 5614622812f47-3eba347aa6fso2529399b6e.3 for ; Mon, 23 Dec 2024 10:09:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734977389; x=1735582189; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=gp/qtE5M5eA2TdzwH3MDMbWKOx23hD1FD2wKulz+4IU=; b=Ndv6PwmddWf5iut8Pl/Ip2/8M3hcqJ5YKB/ZRGgUFLntgX5daWzbJFSC6r3FGTf+aM V/DuYxWzeWl8FX8Go12/59UOY8+c2Fa04KU6PVNgAqU0I6/HHvt1eQUgIziDf+zXWAmu JrP8cBv53quW9kvuB1qycXYfYqF3nULJP7yiMGgyVvzJlF5XtrJaHLutiJurusrnRvnn 2CG+CJQJ5/iJbl5NVQYhUZc472YZfat+RSjEsJRpPBUnXDFfUz4qQaj61YncQ3/2jEwe Z3DrftPo3TNXAi/EuviW4he4SeVf2vIwYOIz0+fzVGEFYy+S30ZfQ4jheuicliQkmkYr jHcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734977389; x=1735582189; h=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=gp/qtE5M5eA2TdzwH3MDMbWKOx23hD1FD2wKulz+4IU=; b=kdDGH4JEH2vec8OH0+pQTDbvLQpXoftKcd2q30x4/vCbgrQmFqP2PC5QEanMmJeV8n wDGcjtfUTLbOokvMa6FxjOAWie6XN9BSozUwihge0fzLwyO2tNZBo2Tg6bVToftnbF99 02LIw9Bu2HFZ/TgcqUvt9oN4Qi2ioKggwKYGChfXbJ5g7c5o66RH7oqRSw6z58855KaT ulbjrMD6p/VXwxbd799kna0R6IVOunme3Iov7qFnIcHmdE2eflKJHULJ9fSHqZiLTWM3 +fWNzc7+zIdK3s565lREF9g/9aAjYUwUHmJdomWFKfVa8KcFnKi4WNtObcpRz2/IqmXJ oczg== X-Gm-Message-State: AOJu0Yy0MOX27xtj2E0dH5+bh/PMF6Wb+Xr27b6Fp9K26ewwSWstQ909 U95CqEKeRMVrV+eacW7D+1GDFjI7TkUtazepbCNFBmcSR0v/kiFahCzWCtzONMwWKYa0m+tss6S zwvDVhurfV+Xrkqf7Z+iPj1jjbOfmpA== X-Gm-Gg: ASbGnctYoHrszRo1GDGNOixu2OX1/qw8W6X+v3nDrCrV5HVeIwJcj0QqhSvnnBoho/L QXjxo8SRTfQ+snloJk877MYrkPCTjVQK5WQB4x6H7ChZAITlywtoCTr+Kmr2DkX+AE0R2gupp X-Google-Smtp-Source: AGHT+IGxVLWIr1JHCmQR7TXPn0VfZ6KjgiI0Ob11M2SIdcvStwLB3pE1IdSTbJ66aOQs4E6wUbbrTnoA6ldYLPV3NnY= X-Received: by 2002:a05:6871:5213:b0:297:28ec:9b26 with SMTP id 586e51a60fabf-2a7fb312901mr7639487fac.33.1734977389185; Mon, 23 Dec 2024 10:09:49 -0800 (PST) MIME-Version: 1.0 References: <06e1f1ee-74b2-43a2-9a63-da20ae455ae2@aklaver.com> In-Reply-To: From: Ron Johnson Date: Mon, 23 Dec 2024 13:09:38 -0500 Message-ID: Subject: Re: Need help in database design To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000f9d2c60629f3e6d1" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f9d2c60629f3e6d1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If your queries all reference userid, then you only need indices on gdid and userid. On Mon, Dec 23, 2024 at 12:49=E2=80=AFPM Divyansh Gupta JNsThMAudy < ag1567827@gmail.com> wrote: > I have one confusion with this design if I opt to create 50 columns I nee= d > to create 50 index which will work with userid index in Bitmap on the oth= er > hand if I create a JSONB column I need to create a single index ? > > On Mon, 23 Dec 2024, 11:10=E2=80=AFpm Ron Johnson, > wrote: > >> Given what you just wrote, I'd stick with 50 separate t* columns. >> Simplifies queries, simplifies updates, and eliminates JSONB conversions= . >> >> On Mon, Dec 23, 2024 at 12:29=E2=80=AFPM Divyansh Gupta JNsThMAudy < >> ag1567827@gmail.com> wrote: >> >>> Values can be updated based on customer actions >>> >>> All rows won't have all 50 key value pairs always if I make those keys >>> into columns the rows might have null value on the other hand if it is >>> JSONB then the key value pair will not be there >>> >>> Yes in UI customers can search for the key value pairs >>> >>> During data population the key value pair will be empty array in case o= f >>> JSONB column or NULL in case of table columns, later when customer perf= orms >>> some actions that time the key value pairs will populate and update, ba= sed >>> on what action customer performs. >>> >>> On Mon, 23 Dec 2024, 10:51=E2=80=AFpm Divyansh Gupta JNsThMAudy, < >>> ag1567827@gmail.com> wrote: >>> >>>> Let's make it more understandable, here is the table schema with 50 >>>> columns in it >>>> >>>> CREATE TABLE dbo.googledocs_tbl ( >>>> gdid int8 GENERATED BY DEFAULT AS IDENTITY( INCREMENT BY 1 MINVALUE 1 >>>> MAXVALUE 9223372036854775807 START 1 CACHE 1 NO CYCLE) NOT NULL, >>>> userid int8 NOT NULL, >>>> t1 int4 NULL, >>>> t2 int4 NULL, >>>> t3 int4 NULL, >>>> t4 int4 NULL, >>>> t5 int4 NULL, >>>> t6 int4 NULL, >>>> t7 int4 NULL, >>>> t8 int4 NULL, >>>> t9 int4 NULL, >>>> t10 int4 NULL, >>>> t11 int4 NULL, >>>> t12 int4 NULL, >>>> t13 int4 NULL, >>>> t14 int4 NULL, >>>> t15 int4 NULL, >>>> t16 int4 NULL, >>>> t17 int4 NULL, >>>> t18 int4 NULL, >>>> t19 int4 NULL, >>>> t20 int4 NULL, >>>> t21 int4 NULL, >>>> t22 int4 NULL, >>>> t23 int4 NULL, >>>> t24 int4 NULL, >>>> t25 int4 NULL, >>>> t26 int4 NULL, >>>> t27 int4 NULL, >>>> t28 int4 NULL, >>>> t29 int4 NULL, >>>> t30 int4 NULL, >>>> t31 int4 NULL, >>>> t32 int4 NULL, >>>> t33 int4 NULL, >>>> t34 int4 NULL, >>>> t35 int4 NULL, >>>> t36 int4 NULL, >>>> t37 int4 NULL, >>>> t38 int4 NULL, >>>> t39 int4 NULL, >>>> t40 int4 NULL, >>>> t41 int4 NULL, >>>> t42 int4 NULL, >>>> t43 int4 NULL, >>>> t44 int4 NULL, >>>> t45 int4 NULL, >>>> t46 int4 NULL, >>>> t47 int4 NULL, >>>> t48 int4 NULL, >>>> t49 int4 NULL, >>>> t50 int4 NULL, >>>> CONSTRAINT googledocs_tbl_pkey PRIMARY KEY (gdid), >>>> ); >>>> >>>> Every time when i query I will query it along with userid >>>> Ex : where userid =3D 12345678 and t1 in (1,2,3) and t2 in (0,1,2) >>>> more key filters if customer applies >>>> >>>> On the other hand if I create a single jsonb column the schema will >>>> look like : >>>> >>>> CREATE TABLE dbo.googledocs_tbl ( >>>> gdid int8 GENERATED BY DEFAULT AS IDENTITY( INCREMENT BY 1 MINVALUE 1 >>>> MAXVALUE 9223372036854775807 START 1 CACHE 1 NO CYCLE) NOT NULL, >>>> userid int8 NOT NULL, >>>> addons_json jsonb default '{}'::jsonb >>>> CONSTRAINT googledocs_tbl_pkey PRIMARY KEY (gdid), >>>> ); >>>> >>>> and the query would be like >>>> where userid =3D 12345678 and ((addons_json @> {t1:1}) or (addons_jso= n @> >>>> {t1:2}) or (addons_json @> {t1:3}) >>>> more key filters if customer applies >>>> >>>> >>>> >>>> On Mon, Dec 23, 2024 at 10:38=E2=80=AFPM David G. Johnston < >>>> david.g.johnston@gmail.com> wrote: >>>> >>>>> >>>>> >>>>> On Mon, Dec 23, 2024, 10:01 Divyansh Gupta JNsThMAudy < >>>>> ag1567827@gmail.com> wrote: >>>>> >>>>>> >>>>>> So here my question is considering one JSONB column is perfect or >>>>>> considering 50 columns will be more optimised. >>>>>> >>>>> The relational database engine is designed around the column-based >>>>> approach. Especially if the columns are generally unchanging, combin= ed >>>>> with using fixed-width data types. >>>>> >>>>> David J. >>>>> >>>>> >> >> -- >> Death to , and butter sauce. >> Don't boil me, I'm still alive. >> lobster! >> > --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000f9d2c60629f3e6d1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If your queries all reference userid, then you only n= eed indices on gdid and userid.

On Mon, Dec 23, 2024 a= t 12:49=E2=80=AFPM Divyansh Gupta JNsThMAudy <ag1567827@gmail.com> wrote:

I have one confusion with t= his design if I opt to create 50 columns I need to create 50 index which wi= ll work with userid index in Bitmap on the other hand if I create a JSONB c= olumn I need to create a single index ?


On Mon= , 23 Dec 2024, 11:10=E2=80=AFpm Ron Johnson, <ronljohnsonjr@gmail.com> wrote:
=
Given what you just wrote, I'd stick with 50 separate t* columns.= =C2=A0 Simplifies queries, simplifies updates, and eliminates JSONB convers= ions.

On Mon, Dec 23, 2024 at 12:29=E2=80=AFPM Divyansh Gupta JNsThMAudy <= ;ag1567827@gmail.com> wrote:

Values can be updated based on customer= actions

All rows won't have all 50 key value pairs always if I m= ake those keys into columns the rows might have null value on the other han= d if it is JSONB then the key value pair will not be there

Yes in UI customers can search for the key value pairs

During data population the key value pair will be empty arra= y in case of JSONB column or NULL in case of table columns, later when cust= omer performs some actions that time the key value pairs will populate and = update, based on what action customer performs.


On Mon= , 23 Dec 2024, 10:51=E2=80=AFpm Divyansh Gupta JNsThMAudy, <ag1567827@g= mail.com> wrote:
Let's make it more understandable, here is the= table schema with 50 columns in it=C2=A0

CREATE TABLE dbo.googledoc= s_tbl (
gdid int8 GENERATED BY DEFAULT AS IDENTITY( INCREMENT BY 1 MINV= ALUE 1 MAXVALUE 9223372036854775807 START 1 CACHE 1 NO CYCLE) NOT NULL,
= userid int8 NOT NULL,
t1 int4 NULL,
t2 int4 NULL,
t3 int4 NULL= ,
t4 int4 NULL,
t5 int4 NULL,
t6 int4 NULL,
t7 int4 NULL, t8 int4 NULL,
t9 int4 NULL,
t10 int4 NULL,
t11 int4 NULL, t12 int4 NULL,
t13 int4 NULL,
t14 int4 NULL,
t15 int4 NULL, t16 int4 NULL,
t17 int4 NULL,
t18 int4 NULL,
t19 int4 NULL,<= br> t20 int4 NULL,
t21 int4 NULL,
t22 int4 NULL,
t23 int4 NULL,=
t24 int4 NULL,
t25 int4 NULL,
t26 int4 NULL,
t27 int4 NULL= ,
t28 int4 NULL,
t29 int4 NULL,
t30 int4 NULL,
t31 int4 NUL= L,
t32 int4 NULL,
t33 int4 NULL,
t34 int4 NULL,
t35 int4 NU= LL,
t36 int4 NULL,
t37 int4 NULL,
t38 int4 NULL,
t39 int4 N= ULL,
t40 int4 NULL,
t41 int4 NULL,
t42 int4 NULL,
t43 int4 = NULL,
t44 int4 NULL,
t45 int4 NULL,
t46 int4 NULL,
t47 int4= NULL,
t48 int4 NULL,
t49 int4 NULL,
t50 int4 NULL,
CONSTRA= INT googledocs_tbl_pkey PRIMARY KEY (gdid),
);

Every time when i = query I will query it along with userid=C2=A0
Ex : where userid =3D 1234= 5678 and t1 in (1,2,3) and t2 in (0,1,2)
more key filters if customer ap= plies=C2=A0

On the other hand if I create a single jsonb column the = schema will look like :

CREATE TABLE dbo.googledocs_tbl (
gdid i= nt8 GENERATED BY DEFAULT AS IDENTITY( INCREMENT BY 1 MINVALUE 1 MAXVALUE 92= 23372036854775807 START 1 CACHE 1 NO CYCLE) NOT NULL,
userid int8 NOT N= ULL,
addons_json jsonb default '{}'::jsonb
CONSTRAINT googl= edocs_tbl_pkey PRIMARY KEY (gdid),
);

and the query would be like= =C2=A0
where userid =3D 12345678 and ((addons_json=C2=A0@> {t1:1}) or= =C2=A0 (addons_json=C2=A0@> {t1:2}) or=C2=A0 (addons_json=C2=A0@> {t1:3})
more key filters = if customer applies=C2=A0



On Mon, Dec 23, 2024 at 10:38=E2= =80=AFPM David G. Johnston <david.g.johnston@gmail.co= m> wrote:


On Mon, Dec 23, 2024, 10:01 Divyansh Gupta JN= sThMAudy <ag1567827@gmail.com> wrote:

So here my question is considering one JSONB column is= perfect or considering 50 columns will be more optimised.

The relational database engine is designed ar= ound the column-based approach.=C2=A0 Especially if the columns are general= ly unchanging, combined with using fixed-width data types.

David J.



--
Death to <Redacted>, and butter sauce.Don't boil me, I'm still alive.
<Redacted> lobs= ter!


--
Death to <Redacted>, and butter sauce.Don't boil me, I'm still alive.
<Redacted> lobs= ter!
--000000000000f9d2c60629f3e6d1--