Re: JSONB Array of Strings (with GIN index) versus Split Rows (B-Tree Index) - Mailing list pgsql-general

From David G. Johnston
Subject Re: JSONB Array of Strings (with GIN index) versus Split Rows (B-Tree Index)
Date
Msg-id CAKFQuwb7RkZVjyCQ=4vJiS_LKmj2pVUB47N991vSPoQohVx9Xg@mail.gmail.com
Whole thread Raw
In response to JSONB Array of Strings (with GIN index) versus Split Rows (B-TreeIndex)  (Syed Jafri <syed.jafri2@ucalgary.ca>)
List pgsql-general
On Sun, Feb 3, 2019 at 10:35 PM Syed Jafri <syed.jafri2@ucalgary.ca> wrote:
> ·         Receiver names are of the type (a-z, 1-5, .)
>
> ·         95% of all queries currently look like this: SELECT * FROM table WHERE Receiver = Alpha, with the new
formatthis would be SELECT * FROM table WHERE receivers @> '"Alpha"'::jsonb; 
> 3.      Which option is more efficient? Which is faster?

I'd probably develop a performance test for the model and planned
queries and experiment with:

1. text arrays
2. jsonb arrays
3. partitioning

David J.


pgsql-general by date:

Previous
From: Ian Zimmerman
Date:
Subject: Re: JSONB Array of Strings (with GIN index) versus Split Rows(B-Tree Index)
Next
From: rob stone
Date:
Subject: Re: Server goes to Recovery Mode when run a SQL