From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Bzzzz <lazyvirus(at)gmx(dot)com>, pgsql-novice(at)lists(dot)postgresql(dot)org |
Subject: | Re: hstore or jsonb ? |
Date: | 2022-11-14 21:03:02 |
Message-ID: | b9cf20b7b7f28c226d7f7980c352449793acf14e.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Mon, 2022-11-14 at 15:50 +0100, Bzzzz wrote:
> I'd like to store specs, as they vary a lot from one item to another,
> hstore or jsonb look like the best solution.
>
> Specs can have 2 levels at most.
> ie: "color": ["white", "black", "blue"]).
>
> The indexation is mandatory for fulltext accurate researches in
> (almost) natural language.
>
> So, as the processing is almost the same (maps I/O in Erlang), which one
> would be the best for my needs, hstore or jsonb ?
"hstore" is obsolete; don't use it.
> Also, from what I read, the both of them can be easily indexed, but
> which index is the best, GIN or RUM ?
>
> And furthermore, which index option (XXX_ops), if any, would be the best
> for the chosen one ?
That depends on the query you need to support.
I have no idea what you mean by "fulltext accurate search" in a hstore
or JSON.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Bzzzz | 2022-11-14 21:21:13 | Re: hstore or jsonb ? |
Previous Message | Bzzzz | 2022-11-14 14:50:57 | hstore or jsonb ? |