f time indexes will be created for the json keys of
>> the JSON values in this column.
>> For e.g. on "name", "address" , "country" now. Later I can have another
>> key and index like on "continent".
>>
>> As per postgresql limitati
No matter what you do, you will not typically get the same level of
performance as normalized tables as you do not get statistics on the values
stored in your jsonb column. No knowledge of null fraction, number of
distinct values, or most common values and their frequencies.
is column.
> For e.g. on "name", "address" , "country" now. Later I can have another
> key and index like on "continent".
>
> As per postgresql limitations there are limits on the indexes. So I
> understand we can create many indexes.
>
> But
".
As per postgresql limitations there are limits on the indexes. So I
understand we can create many indexes.
But obviously I understand creating many indexes will impact write
performance and space will be utilized.
Would like to know if creating indexes in this manner can create any other
issues or inputs on the whole topic of indexes in JSONB types.
Best Regards,
Saurav