public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: Divyansh Gupta JNsThMAudy <[email protected]>
Cc: [email protected]
Subject: Re: Need help in database design
Date: Mon, 23 Dec 2024 08:54:04 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAHesJ5JbkCBZ2f_AvUr8+KWnGPAsobu4zyfnWm8bEeb7X9oqDQ@mail.gmail.com>
References: <CAHesJ5LES3aTDf=xp7NOwrADQ_HWC-Spsv7yLu9ZY+zxzZO53A@mail.gmail.com>
<[email protected]>
<CAHesJ5+ASNoSNMiC5Ms0Ts=gw7v2_UeBpUT=phujO4yE_XCbEw@mail.gmail.com>
<CAHesJ5JbkCBZ2f_AvUr8+KWnGPAsobu4zyfnWm8bEeb7X9oqDQ@mail.gmail.com>
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,
> <[email protected] <mailto:[email protected]>> 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,
> <[email protected] <mailto:[email protected]>> 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
> [email protected] <mailto:[email protected]>
>
--
Adrian Klaver
[email protected]
view thread (13+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Need help in database design
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox