Date: Tue, 15 Nov 2022 09:39:46 +0100
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Bzzzz <lazyvirus@gmx.com>, pgsql-novice@lists.postgresql.org
Subject: Re: hstore or jsonb ?
Message-ID: <Y3NQUlvvYrXZFVs3@depesz.com>
Reply-To: depesz@depesz.com
References: <20221114155057.48406b86@msi.defcon1.lan>
 <b9cf20b7b7f28c226d7f7980c352449793acf14e.camel@cybertec.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <b9cf20b7b7f28c226d7f7980c352449793acf14e.camel@cybertec.at>
Archived-At: 
 <https://www.postgresql.org/message-id/Y3NQUlvvYrXZFVs3%40depesz.com>
Precedence: bulk

On Mon, Nov 14, 2022 at 10:03:02PM +0100, Laurenz Albe wrote:
> 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.

Do you have any support for this claim?

Best regards,

depesz