Message-ID: <b9cf20b7b7f28c226d7f7980c352449793acf14e.camel@cybertec.at>
Subject: Re: hstore or jsonb ?
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Bzzzz <lazyvirus@gmx.com>, pgsql-novice@lists.postgresql.org
Date: Mon, 14 Nov 2022 22:03:02 +0100
In-Reply-To: <20221114155057.48406b86@msi.defcon1.lan>
References: <20221114155057.48406b86@msi.defcon1.lan>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/b9cf20b7b7f28c226d7f7980c352449793acf14e.camel%40cybertec.at>
Precedence: bulk

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