Need help in logical replication
Hii PostgreSQL Community, I am setting up logical replication between two clusters in the same subnet group. I’ve created a publication on the primary and a subscription on the secondary, and the replication slot has been created. However, the slot remains inactive, and changes aren’t being applied on the subscriber. I am using AWS RDS for that Could you please help me identify the possible cause and resolution for this issue? Thank you in advance! [image: image.png] [image: image.png] CREATE PUBLICATION logical_replication_test FOR TABLE dbo.logical_rep_test; CREATE SUBSCRIPTION logical_replication_test_su CONNECTION 'conn_strig' PUBLICATION logical_replication_test;
Re: Need help in logical replication
Thank you for the response Justin found and fixed the error On Mon, 13 Jan 2025, 10:15 pm Justin, wrote: > Hi Divyansh, > > Go to the subscriber and look for errors in the PostgreSQL logs. > > When creating a subscription the default action is to sync the tables. Is > the subscriber table empty?? > > Thank you, > > On Mon, Jan 13, 2025 at 7:30 AM Divyansh Gupta JNsThMAudy < > ag1567...@gmail.com> wrote: > >> Hii PostgreSQL Community, >> >> I am setting up logical replication between two clusters in the same >> subnet group. I’ve created a publication on the primary and a subscription >> on the secondary, and the replication slot has been created. However, the >> slot remains inactive, and changes aren’t being applied on the subscriber. >> >> I am using AWS RDS for that >> >> Could you please help me identify the possible cause and resolution for >> this issue? >> >> Thank you in advance! >> >> [image: image.png] >> [image: image.png] >> >> CREATE PUBLICATION logical_replication_test >> >> FOR TABLE dbo.logical_rep_test; >> >> CREATE SUBSCRIPTION logical_replication_test_su >> >> CONNECTION 'conn_strig' >> >> PUBLICATION logical_replication_test; >> >>
Need help in database design
Hii Community, I need to provide a support for some functionality for my application for that I need to store 50 key value pair set, so I am in a dilemma, weather I create 50 new columns of int2 data type each column will contain value of a specific key or should I go with JSONB data type with 50 key value pair, the table on which I am going to do that all contains 1 Billion rows of data and have 84 hash partitions, I have gone through multiple articles some of them mentioned it's a good approach to create 50 new columns and some states that creating one JSONB would be best that's why I need your help to move forward, also I am ready to make H-Store instead of JSONB if it provides better performance. Please help me to comes out from that dilemma. Regards, Divyansh Gupta, Database Administrator
Re: Need help in database design
As per the discussion with other team members they suggested if we store 50 values for keys in an individual column that will provide better performance as the data type is native (INT2) on the other hand if we store all the key value pair in a single JSONB column the performance will degrade even after applying a GIN index on that however the statement sounds funny but I want to take everyone openion? On Mon, 23 Dec 2024, 10:05 pm Adrian Klaver, wrote: > On 12/23/24 07:53, Divyansh Gupta JNsThMAudy wrote: > > Hii Community, > > > > I need to provide a support for some functionality for my application > > for that I need to store 50 key value pair set, so I am in a dilemma, > > weather I create 50 new columns of int2 data type each column will > > This is unclear, I am trying to figure out you go from '50 key value > pair set' to '50 new columns of int2'. > > In other words how 50 pairs turn into 50 columns? > > Then there is the question of why 50 keys per row in the first place? > > > > contain value of a specific key or should I go with JSONB data type with > > 50 key value pair, the table on which I am going to do that all contains > > 1 Billion rows of data and have 84 hash partitions, I have gone through > > multiple articles some of them mentioned it's a good approach to create > > 50 new columns and some states that creating one JSONB would be best > > that's why I need your help to move forward, also I am ready to make > > H-Store instead of JSONB if it provides better performance. > > Please help me to comes out from that dilemma. > > > > Regards, > > Divyansh Gupta, > > Database Administrator > > -- > Adrian Klaver > adrian.kla...@aklaver.com > >
Re: Need help in database design
Also as you ask how 50 pairs turns into 50 column so each column will be a key and the value of that key will store inside their respective column for each row On Mon, 23 Dec 2024, 10:14 pm Divyansh Gupta JNsThMAudy, < ag1567...@gmail.com> wrote: > As per the discussion with other team members they suggested if we store > 50 values for keys in an individual column that will provide better > performance as the data type is native (INT2) on the other hand if we store > all the key value pair in a single JSONB column the performance will > degrade even after applying a GIN index on that however the statement > sounds funny but I want to take everyone openion? > > On Mon, 23 Dec 2024, 10:05 pm Adrian Klaver, > wrote: > >> On 12/23/24 07:53, Divyansh Gupta JNsThMAudy wrote: >> > Hii Community, >> > >> > I need to provide a support for some functionality for my application >> > for that I need to store 50 key value pair set, so I am in a dilemma, >> > weather I create 50 new columns of int2 data type each column will >> >> This is unclear, I am trying to figure out you go from '50 key value >> pair set' to '50 new columns of int2'. >> >> In other words how 50 pairs turn into 50 columns? >> >> Then there is the question of why 50 keys per row in the first place? >> >> >> > contain value of a specific key or should I go with JSONB data type >> with >> > 50 key value pair, the table on which I am going to do that all >> contains >> > 1 Billion rows of data and have 84 hash partitions, I have gone through >> > multiple articles some of them mentioned it's a good approach to create >> > 50 new columns and some states that creating one JSONB would be best >> > that's why I need your help to move forward, also I am ready to make >> > H-Store instead of JSONB if it provides better performance. >> > Please help me to comes out from that dilemma. >> > >> > Regards, >> > Divyansh Gupta, >> > Database Administrator >> >> -- >> Adrian Klaver >> adrian.kla...@aklaver.com >> >>
Re: Need help in database design
Sure , for example, I have 50 key with name as t1 , t2 ,t3 ...t50
Now each key could have values from 0 to 3
So let suppose we have JSONB like that for row r1
{
t1: 1
t2: 2
t3 : 3
}
As if I convert it into columns so r1 will have
t1 column will contain 1
t2 column will contain 2
.. So on
So here my question is considering one JSONB column is perfect or
considering 50 columns will be more optimised.
On Mon, 23 Dec 2024, 10:24 pm Adrian Klaver,
wrote:
> On 12/23/24 08:46, Divyansh Gupta JNsThMAudy wrote:
> > Also as you ask how 50 pairs turns into 50 column so each column will be
> > a key and the value of that key will store inside their respective
> > column for each row
>
> My problem with understanding this is 50 pairs = 100 values, I don't
> understand how that can fit in 50 columns that can only handle 1 value
> each. You need to provide some example data showing what you want to
> achieve. It does not need to be the full 50, just something to show the
> process.
>
>
> >
> >
> > On Mon, 23 Dec 2024, 10:14 pm Divyansh Gupta JNsThMAudy,
> > mailto:ag1567...@gmail.com>> wrote:
> >
> > As per the discussion with other team members they suggested if we
> > store 50 values for keys in an individual column that will provide
> > better performance as the data type is native (INT2) on the other
> > hand if we store all the key value pair in a single JSONB column the
> > performance will degrade even after applying a GIN index on that
> > however the statement sounds funny but I want to take everyone
> openion?
> >
> >
> > On Mon, 23 Dec 2024, 10:05 pm Adrian Klaver,
> > mailto:adrian.kla...@aklaver.com>>
> wrote:
> >
> > On 12/23/24 07:53, Divyansh Gupta JNsThMAudy wrote:
> > > Hii Community,
> > >
> > > I need to provide a support for some functionality for my
> > application
> > > for that I need to store 50 key value pair set, so I am in a
> > dilemma,
> > > weather I create 50 new columns of int2 data type each column
> > will
> >
> > This is unclear, I am trying to figure out you go from '50 key
> > value
> > pair set' to '50 new columns of int2'.
> >
> > In other words how 50 pairs turn into 50 columns?
> >
> > Then there is the question of why 50 keys per row in the first
> > place?
> >
> >
> > > contain value of a specific key or should I go with JSONB
> > data type with
> > > 50 key value pair, the table on which I am going to do that
> > all contains
> > > 1 Billion rows of data and have 84 hash partitions, I have
> > gone through
> > > multiple articles some of them mentioned it's a good approach
> > to create
> > > 50 new columns and some states that creating one JSONB would
> > be best
> > > that's why I need your help to move forward, also I am ready
> > to make
> > > H-Store instead of JSONB if it provides better performance.
> > > Please help me to comes out from that dilemma.
> > >
> > > Regards,
> > > Divyansh Gupta,
> > > Database Administrator
> >
> > --
> > Adrian Klaver
> > adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>
> >
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>
>
Re: Need help in database design
Empty JSONB by mistake, I wrote array sorry about that
On Mon, 23 Dec 2024, 10:59 pm Divyansh Gupta JNsThMAudy, <
ag1567...@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 of
> JSONB column or NULL in case of table columns, later when customer 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 pm Divyansh Gupta JNsThMAudy, <
> ag1567...@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 = 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 = 12345678 and ((addons_json @> {t1:1}) or (addons_json @>
>> {t1:2}) or (addons_json @> {t1:3})
>> more key filters if customer applies
>>
>>
>>
>> On Mon, Dec 23, 2024 at 10:38 PM David G. Johnston <
>> david.g.johns...@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Dec 23, 2024, 10:01 Divyansh Gupta JNsThMAudy <
>>> ag1567...@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, combined
>>> with using fixed-width data types.
>>>
>>> David J.
>>>
>>>
Re: Need help in database design
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 = 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 = 12345678 and ((addons_json @> {t1:1}) or (addons_json @>
{t1:2}) or (addons_json @> {t1:3})
more key filters if customer applies
On Mon, Dec 23, 2024 at 10:38 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
>
>
> On Mon, Dec 23, 2024, 10:01 Divyansh Gupta JNsThMAudy
> 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, combined
> with using fixed-width data types.
>
> David J.
>
>
Re: Need help in database design
Thank you everyone for giving your valuable responses, I am glad that everyone understands my concern. I got some good ideas about the database design that I am following after going through some stress testing I will implement the same. Thank you so much Everyone On Tue, 24 Dec 2024, 12:09 am Ron Johnson, wrote: > Are these columns really unique for all 20M rows that a userid can have in > the table? I'm dubious. > > Split a LOT of those columns out into a separate table named "user" with > PK userid. It'll save a huge amount of disk space, and speed up queries by > not having to fetch it all every time. > > useremail varchar(600) NOT NULL, > title public.citext NULL, > authorname varchar(600) NULL, > authoremail varchar(600) NULL, > updated varchar(300) NOT NULL, > entryid varchar(2000) NOT NULL, > lastmodifiedby varchar(600) NULL, > lastmodifiedbyemail varchar(600) NULL, > "size" varchar(300) NULL, > contenttype varchar(250) NULL, > fileextension varchar(50) NULL, > docfoldername public.citext NULL, > folderresourceid public.citext NULL, > filesize int8 DEFAULT 0 NOT NULL, > retentionstatus int2 DEFAULT 0 NOT NULL, > docfileref int8 NULL, > usid int4 NULL, > archivepath varchar(500) NULL, > createddate timestamp(6) DEFAULT NULL::timestamp without time zone NULL, > zipfilename varchar(100) NULL, > oncreatedat timestamp(6) DEFAULT clock_timestamp() NOT NULL, > onupdateat timestamp(6) DEFAULT clock_timestamp() NOT NULL, > startsnapshot int4 DEFAULT 0 NOT NULL, > currentsnapshot int4 DEFAULT 0 NOT NULL, > dismiss int2 DEFAULT 0 NOT NULL, > checksum varchar NULL, > typeoffile int2 GENERATED ALWAYS AS ( > > > > On Mon, Dec 23, 2024 at 1:32 PM Divyansh Gupta JNsThMAudy < > ag1567...@gmail.com> wrote: > >> Currently I haven't created those columns , I have created addons_json >> column which is a JSONB column yet in a discussion weather I should create >> or consider only one JSONB column. >> >> On Tue, 24 Dec 2024, 12:00 am Divyansh Gupta JNsThMAudy, < >> ag1567...@gmail.com> wrote: >> >>> Range partition can help when you applies filter for a specific range >>> but in my case I need to apply filter on userid always, however I have date >>> columns but there is less variation in timestamp which I have that's why >>> didn't go for range partition. >>> >>> On Mon, 23 Dec 2024, 11:57 pm Ron Johnson, >>> wrote: >>> >>>> >>>> 1. I bet you'd get better performance using RANGE partitioning. >>>> 2. Twenty million rows per userid is a *LOT*. No subdivisions (like >>>> date range)? >>>> >>>> On Mon, Dec 23, 2024 at 1:23 PM Divyansh Gupta JNsThMAudy < >>>> ag1567...@gmail.com> wrote: >>>> >>>>> Adrian, Please check this out; >>>>> >>>>> PARTITION BY HASH (userid); CREATE TABLE dbo. >>>>> googledocs_tbl_clone_part_0 PARTITION OF dbo.googledocs_tbl_clone FOR >>>>> VALUES WITH (modulus 84, remainder 0); ... CREATE TABLE dbo. >>>>> googledocs_tbl_clone_part_83 PARTITION OF dbo.googledocs_tbl_clone FOR >>>>> VALUES WITH (modulus 84, remainder 83); >>>>> >>>>> On Mon, Dec 23, 2024 at 11:48 PM Divyansh Gupta JNsThMAudy < >>>>> ag1567...@gmail.com> wrote: >>>>> >>>>>> Adrian, the partition is on userid using hash partition with 84 >>>>>> partitions >>>>>> >>>>>> Ron, there could be more than 20 Million records possible for a >>>>>> single userid in that case if I create index on userid only not on other >>>>>> column the query is taking more than 30 seconds to return the results. >>>>>> >>>>>> On Mon, 23 Dec 2024, 11:40 pm Ron Johnson, >>>>>> wrote: >>>>>> >>>>>>> If your queries all reference userid, then you only need indices on >>>>>>> gdid and userid. >>>>>>> >>>>>>> On Mon, Dec 23, 2024 at 12:49 PM Divyansh Gupta JNsThMAudy < >>>>>>> ag1567...@gmail.com> wrote: >>>>>>> >>>>>>>> I have one confusion with this design if I opt to create 50 columns >>>>>>>> I need to create 50 index which will work with userid index in Bitmap >>>>>>>> on >>>>>>>> the other hand if I create a JSONB column I need to create a single >>>>>>>> index ? >
Re: Need help in database design
The current application does not have support for that, If I go for that, it will require a lot of effort from the team which Is not possible right now. On Tue, 24 Dec 2024, 12:47 am , wrote: > Just out of curiosity, not suggestion this is the solution. Why save json > in PostgreSQL and not in a DB specialised on JSON like MongoDB? > > Divyansh Gupta JNsThMAudy escribió: > > Thank you everyone for giving your valuable responses, I am glad that > everyone understands my concern. I got some good ideas about the database > design that I am following after going through some stress testing I will > implement the same. > > Thank you so much Everyone > >
Re: Need help in database design
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 of
JSONB column or NULL in case of table columns, later when customer 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 pm Divyansh Gupta JNsThMAudy, <
ag1567...@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 = 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 = 12345678 and ((addons_json @> {t1:1}) or (addons_json @>
> {t1:2}) or (addons_json @> {t1:3})
> more key filters if customer applies
>
>
>
> On Mon, Dec 23, 2024 at 10:38 PM David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>
>>
>>
>> On Mon, Dec 23, 2024, 10:01 Divyansh Gupta JNsThMAudy <
>> ag1567...@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, combined
>> with using fixed-width data types.
>>
>> David J.
>>
>>
Re: Need help in database design
Ron here is the entire table schema FYI, userid is the mandate column on
which filter is always applies:
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,
useremail varchar(600) NOT NULL,
title public.citext NULL,
authorname varchar(600) NULL,
authoremail varchar(600) NULL,
updated varchar(300) NOT NULL,
entryid varchar(2000) NOT NULL,
lastmodifiedby varchar(600) NULL,
lastmodifiedbyemail varchar(600) NULL,
"size" varchar(300) NULL,
contenttype varchar(250) NULL,
fileextension varchar(50) NULL,
docfoldername public.citext NULL,
folderresourceid public.citext NULL,
filesize int8 DEFAULT 0 NOT NULL,
retentionstatus int2 DEFAULT 0 NOT NULL,
docfileref int8 NULL,
usid int4 NULL,
archivepath varchar(500) NULL,
createddate timestamp(6) DEFAULT NULL::timestamp without time zone NULL,
zipfilename varchar(100) NULL,
oncreatedat timestamp(6) DEFAULT clock_timestamp() NOT NULL,
onupdateat timestamp(6) DEFAULT clock_timestamp() NOT NULL,
startsnapshot int4 DEFAULT 0 NOT NULL,
currentsnapshot int4 DEFAULT 0 NOT NULL,
dismiss int2 DEFAULT 0 NOT NULL,
checksum varchar NULL,
typeoffile int2 GENERATED ALWAYS AS (
CASE
WHEN authoremail::text = useremail::text THEN 0::smallint
ELSE 1::smallint
END) STORED NOT NULL,
parquetfilename varchar(100) NULL,
metadata_vector tsvector GENERATED ALWAYS AS (to_tsvector('english'::
regconfig, (COALESCE(title::character varying, ''::text::character
varying)::text || ' '::text) || (COALESCE(docfoldername::text, ''::text) || '
'::text)) || (COALESCE(authorname, ''::text::character varying)::text || ' '
::text)) || (COALESCE(fileextension, ''::text::character varying)::text || '
'::text)) || (COALESCE(lastmodifiedby, ''::text::character varying)::text
|| ' '::text)) || COALESCE(contenttype, ''::character varying::text::
character varying)::text)) STORED NULL,
isfileencrypted int4 DEFAULT 0 NULL,
addons_json jsonb DEFAULT '{}'::jsonb NULL,
CONSTRAINT googledocs_tbl_clone_pkey PRIMARY KEY (gdid, userid),
CONSTRAINT fk_googledocs_tbl_clone_users_tbl FOREIGN KEY (userid) REFERENCES
dbo.users_tbl(uid) ON DELETE CASCADE
)
PARTITION BY HASH (userid);
On Mon, Dec 23, 2024 at 11:53 PM Divyansh Gupta JNsThMAudy <
ag1567...@gmail.com> wrote:
> Adrian, Please check this out;
>
> PARTITION BY HASH (userid); CREATE TABLE dbo.googledocs_tbl_clone_part_0
> PARTITION OF dbo.googledocs_tbl_clone FOR VALUES WITH (modulus 84,
> remainder 0); ... CREATE TABLE dbo.googledocs_tbl_clone_part_83 PARTITION
> OF dbo.googledocs_tbl_clone FOR VALUES WITH (modulus 84, remainder 83);
>
> On Mon, Dec 23, 2024 at 11:48 PM Divyansh Gupta JNsThMAudy <
> ag1567...@gmail.com> wrote:
>
>> Adrian, the partition is on userid using hash partition with 84 partitions
>>
>> Ron, there could be more than 20 Million records possible for a single
>> userid in that case if I create index on userid only not on other column
>> the query is taking more than 30 seconds to return the results.
>>
>> On Mon, 23 Dec 2024, 11:40 pm Ron Johnson,
>> wrote:
>>
>>> If your queries all reference userid, then you only need indices on gdid
>>> and userid.
>>>
>>> On Mon, Dec 23, 2024 at 12:49 PM Divyansh Gupta JNsThMAudy <
>>> ag1567...@gmail.com> wrote:
>>>
>>>> I have one confusion with this design if I opt to create 50 columns I
>>>> need to create 50 index which will work with userid index in Bitmap on the
>>>> other hand if I create a JSONB column I need to create a single index ?
>>>>
>>>> On Mon, 23 Dec 2024, 11:10 pm 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 PM Divyansh Gupta JNsThMAudy <
>>>>> ag1567...@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
Re: Need help in database design
Range partition can help when you applies filter for a specific range but in my case I need to apply filter on userid always, however I have date columns but there is less variation in timestamp which I have that's why didn't go for range partition. On Mon, 23 Dec 2024, 11:57 pm Ron Johnson, wrote: > > 1. I bet you'd get better performance using RANGE partitioning. > 2. Twenty million rows per userid is a *LOT*. No subdivisions (like date > range)? > > On Mon, Dec 23, 2024 at 1:23 PM Divyansh Gupta JNsThMAudy < > ag1567...@gmail.com> wrote: > >> Adrian, Please check this out; >> >> PARTITION BY HASH (userid); CREATE TABLE dbo.googledocs_tbl_clone_part_0 >> PARTITION OF dbo.googledocs_tbl_clone FOR VALUES WITH (modulus 84, >> remainder 0); ... CREATE TABLE dbo.googledocs_tbl_clone_part_83 PARTITION >> OF dbo.googledocs_tbl_clone FOR VALUES WITH (modulus 84, remainder 83); >> >> On Mon, Dec 23, 2024 at 11:48 PM Divyansh Gupta JNsThMAudy < >> ag1567...@gmail.com> wrote: >> >>> Adrian, the partition is on userid using hash partition with 84 >>> partitions >>> >>> Ron, there could be more than 20 Million records possible for a single >>> userid in that case if I create index on userid only not on other column >>> the query is taking more than 30 seconds to return the results. >>> >>> On Mon, 23 Dec 2024, 11:40 pm Ron Johnson, >>> wrote: >>> >>>> If your queries all reference userid, then you only need indices on >>>> gdid and userid. >>>> >>>> On Mon, Dec 23, 2024 at 12:49 PM Divyansh Gupta JNsThMAudy < >>>> ag1567...@gmail.com> wrote: >>>> >>>>> I have one confusion with this design if I opt to create 50 columns I >>>>> need to create 50 index which will work with userid index in Bitmap on the >>>>> other hand if I create a JSONB column I need to create a single index ? >>>>> >>>>> On Mon, 23 Dec 2024, 11:10 pm 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 PM Divyansh Gupta JNsThMAudy < >>>>>> ag1567...@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 of JSONB column or NULL in case of table columns, later when >>>>>>> customer >>>>>>> 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 pm Divyansh Gupta JNsThMAudy, < >>>>>>> ag1567...@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, >>>>>>>> t
Re: Need help in database design
Adrian, Please check this out; PARTITION BY HASH (userid); CREATE TABLE dbo.googledocs_tbl_clone_part_0 PARTITION OF dbo.googledocs_tbl_clone FOR VALUES WITH (modulus 84, remainder 0); ... CREATE TABLE dbo.googledocs_tbl_clone_part_83 PARTITION OF dbo. googledocs_tbl_clone FOR VALUES WITH (modulus 84, remainder 83); On Mon, Dec 23, 2024 at 11:48 PM Divyansh Gupta JNsThMAudy < ag1567...@gmail.com> wrote: > Adrian, the partition is on userid using hash partition with 84 partitions > > Ron, there could be more than 20 Million records possible for a single > userid in that case if I create index on userid only not on other column > the query is taking more than 30 seconds to return the results. > > On Mon, 23 Dec 2024, 11:40 pm Ron Johnson, > wrote: > >> If your queries all reference userid, then you only need indices on gdid >> and userid. >> >> On Mon, Dec 23, 2024 at 12:49 PM Divyansh Gupta JNsThMAudy < >> ag1567...@gmail.com> wrote: >> >>> I have one confusion with this design if I opt to create 50 columns I >>> need to create 50 index which will work with userid index in Bitmap on the >>> other hand if I create a JSONB column I need to create a single index ? >>> >>> On Mon, 23 Dec 2024, 11:10 pm 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 PM Divyansh Gupta JNsThMAudy < >>>> ag1567...@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 >>>>> of JSONB column or NULL in case of table columns, later when customer >>>>> 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 pm Divyansh Gupta JNsThMAudy, < >>>>> ag1567...@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 NU
Re: Need help in database design
Currently I haven't created those columns , I have created addons_json column which is a JSONB column yet in a discussion weather I should create or consider only one JSONB column. On Tue, 24 Dec 2024, 12:00 am Divyansh Gupta JNsThMAudy, < ag1567...@gmail.com> wrote: > Range partition can help when you applies filter for a specific range but > in my case I need to apply filter on userid always, however I have date > columns but there is less variation in timestamp which I have that's why > didn't go for range partition. > > On Mon, 23 Dec 2024, 11:57 pm Ron Johnson, > wrote: > >> >> 1. I bet you'd get better performance using RANGE partitioning. >> 2. Twenty million rows per userid is a *LOT*. No subdivisions (like >> date range)? >> >> On Mon, Dec 23, 2024 at 1:23 PM Divyansh Gupta JNsThMAudy < >> ag1567...@gmail.com> wrote: >> >>> Adrian, Please check this out; >>> >>> PARTITION BY HASH (userid); CREATE TABLE dbo.googledocs_tbl_clone_part_0 >>> PARTITION OF dbo.googledocs_tbl_clone FOR VALUES WITH (modulus 84, >>> remainder 0); ... CREATE TABLE dbo.googledocs_tbl_clone_part_83 >>> PARTITION OF dbo.googledocs_tbl_clone FOR VALUES WITH (modulus 84, >>> remainder 83); >>> >>> On Mon, Dec 23, 2024 at 11:48 PM Divyansh Gupta JNsThMAudy < >>> ag1567...@gmail.com> wrote: >>> >>>> Adrian, the partition is on userid using hash partition with 84 >>>> partitions >>>> >>>> Ron, there could be more than 20 Million records possible for a single >>>> userid in that case if I create index on userid only not on other column >>>> the query is taking more than 30 seconds to return the results. >>>> >>>> On Mon, 23 Dec 2024, 11:40 pm Ron Johnson, >>>> wrote: >>>> >>>>> If your queries all reference userid, then you only need indices on >>>>> gdid and userid. >>>>> >>>>> On Mon, Dec 23, 2024 at 12:49 PM Divyansh Gupta JNsThMAudy < >>>>> ag1567...@gmail.com> wrote: >>>>> >>>>>> I have one confusion with this design if I opt to create 50 columns I >>>>>> need to create 50 index which will work with userid index in Bitmap on >>>>>> the >>>>>> other hand if I create a JSONB column I need to create a single index ? >>>>>> >>>>>> On Mon, 23 Dec 2024, 11:10 pm 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 PM Divyansh Gupta JNsThMAudy < >>>>>>> ag1567...@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 of JSONB column or NULL in case of table columns, later when >>>>>>>> customer >>>>>>>> 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 pm Divyansh Gupta JNsThMAudy, < >>>>>>>> ag1567...@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, >>
Re: Need help in database design
I have one confusion with this design if I opt to create 50 columns I need
to create 50 index which will work with userid index in Bitmap on the other
hand if I create a JSONB column I need to create a single index ?
On Mon, 23 Dec 2024, 11:10 pm 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 PM Divyansh Gupta JNsThMAudy <
> ag1567...@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 of
>> JSONB column or NULL in case of table columns, later when customer 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 pm Divyansh Gupta JNsThMAudy, <
>> ag1567...@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 = 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 = 12345678 and ((addons_json @> {t1:1}) or (addons_json @>
>>> {t1:2}) or (addons_json @> {t1:3})
>>> more key filters if customer applies
>>>
>>>
>>>
>>> On Mon, Dec 23, 2024 at 10:38 PM David G. Johnston <
>>> david.g.johns...@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Dec 23, 2024, 10:01 Divyansh Gupta JNsThMAudy <
>>>> ag1567...@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, combined
>>>> with using fixed-width data types.
>>>>
>>>> David J.
>>>>
>>>>
>
> --
> Death to , and butter sauce.
> Don't boil me, I'm still alive.
> lobster!
>
Re: Need help in database design
Each row have a PK (gdid) that will uniquely refrence 50 k/v pair set
On Mon, 23 Dec 2024, 10:35 pm Ron Johnson, wrote:
> How do you uniquely reference each set of 50 k/v pairs?
>
> On Mon, Dec 23, 2024 at 12:01 PM Divyansh Gupta JNsThMAudy <
> ag1567...@gmail.com> wrote:
>
>> Sure , for example, I have 50 key with name as t1 , t2 ,t3 ...t50
>>
>> Now each key could have values from 0 to 3
>>
>> So let suppose we have JSONB like that for row r1
>>
>> {
>>
>> t1: 1
>>
>> t2: 2
>>
>> t3 : 3
>>
>> }
>>
>>
>> As if I convert it into columns so r1 will have
>>
>> t1 column will contain 1
>>
>> t2 column will contain 2
>>
>> .. So on
>>
>>
>> So here my question is considering one JSONB column is perfect or
>> considering 50 columns will be more optimised.
>>
>>
>>
>> On Mon, 23 Dec 2024, 10:24 pm Adrian Klaver,
>> wrote:
>>
>>> On 12/23/24 08:46, Divyansh Gupta JNsThMAudy wrote:
>>> > Also as you ask how 50 pairs turns into 50 column so each column will
>>> be
>>> > a key and the value of that key will store inside their respective
>>> > column for each row
>>>
>>> My problem with understanding this is 50 pairs = 100 values, I don't
>>> understand how that can fit in 50 columns that can only handle 1 value
>>> each. You need to provide some example data showing what you want to
>>> achieve. It does not need to be the full 50, just something to show the
>>> process.
>>>
>>>
>>> >
>>> >
>>> > On Mon, 23 Dec 2024, 10:14 pm Divyansh Gupta JNsThMAudy,
>>> > mailto:ag1567...@gmail.com>> wrote:
>>> >
>>> > As per the discussion with other team members they suggested if we
>>> > store 50 values for keys in an individual column that will provide
>>> > better performance as the data type is native (INT2) on the other
>>> > hand if we store all the key value pair in a single JSONB column
>>> the
>>> > performance will degrade even after applying a GIN index on that
>>> > however the statement sounds funny but I want to take everyone
>>> openion?
>>> >
>>> >
>>> > On Mon, 23 Dec 2024, 10:05 pm Adrian Klaver,
>>> > mailto:adrian.kla...@aklaver.com>>
>>> wrote:
>>> >
>>> > On 12/23/24 07:53, Divyansh Gupta JNsThMAudy wrote:
>>> > > Hii Community,
>>> > >
>>> > > I need to provide a support for some functionality for my
>>> > application
>>> > > for that I need to store 50 key value pair set, so I am in a
>>> > dilemma,
>>> > > weather I create 50 new columns of int2 data type each
>>> column
>>> > will
>>> >
>>> > This is unclear, I am trying to figure out you go from '50 key
>>> > value
>>> > pair set' to '50 new columns of int2'.
>>> >
>>> > In other words how 50 pairs turn into 50 columns?
>>> >
>>> > Then there is the question of why 50 keys per row in the first
>>> > place?
>>> >
>>> >
>>> > > contain value of a specific key or should I go with JSONB
>>> > data type with
>>> > > 50 key value pair, the table on which I am going to do that
>>> > all contains
>>> > > 1 Billion rows of data and have 84 hash partitions, I have
>>> > gone through
>>> > > multiple articles some of them mentioned it's a good
>>> approach
>>> > to create
>>> > > 50 new columns and some states that creating one JSONB would
>>> > be best
>>> > > that's why I need your help to move forward, also I am ready
>>> > to make
>>> > > H-Store instead of JSONB if it provides better performance.
>>> > > Please help me to comes out from that dilemma.
>>> > >
>>> > > Regards,
>>> > > Divyansh Gupta,
>>> > > Database Administrator
>>> >
>>> > --
>>> > Adrian Klaver
>>> > adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>
>>> >
>>>
>>> --
>>> Adrian Klaver
>>> adrian.kla...@aklaver.com
>>>
>>>
>
> --
> Death to , and butter sauce.
> Don't boil me, I'm still alive.
> lobster!
>
Re: Need help in database design
Adrian, the partition is on userid using hash partition with 84 partitions
Ron, there could be more than 20 Million records possible for a single
userid in that case if I create index on userid only not on other column
the query is taking more than 30 seconds to return the results.
On Mon, 23 Dec 2024, 11:40 pm Ron Johnson, wrote:
> If your queries all reference userid, then you only need indices on gdid
> and userid.
>
> On Mon, Dec 23, 2024 at 12:49 PM Divyansh Gupta JNsThMAudy <
> ag1567...@gmail.com> wrote:
>
>> I have one confusion with this design if I opt to create 50 columns I
>> need to create 50 index which will work with userid index in Bitmap on the
>> other hand if I create a JSONB column I need to create a single index ?
>>
>> On Mon, 23 Dec 2024, 11:10 pm 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 PM Divyansh Gupta JNsThMAudy <
>>> ag1567...@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
>>>> of JSONB column or NULL in case of table columns, later when customer
>>>> 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 pm Divyansh Gupta JNsThMAudy, <
>>>> ag1567...@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 = 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 = 12345678 and ((addons_json @> {t1:1}) or (addons_json @>
>>>>> {t1:2}) or (addons_json @> {t1:3})
>>>>> more key filters if customer applies
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Dec 23, 2024 at 10:38 PM David G. Johnston <
>>>>> david.g.johns...@gmail.com> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Dec 23, 2024, 10:01 Divyansh Gupta JNsThMAudy <
>>>>>> ag1567...@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, combined
>>>>>> with using fixed-width data types.
>>>>>>
>>>>>> David J.
>>>>>>
>>>>>>
>>>
>>> --
>>> Death to , and butter sauce.
>>> Don't boil me, I'm still alive.
>>> lobster!
>>>
>>
>
> --
> Death to , and butter sauce.
> Don't boil me, I'm still alive.
> lobster!
>
