Re: Reproducible coliisions in jsonb_hash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Valeriy Meleshkin <valeriy(at)meleshk(dot)in>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reproducible coliisions in jsonb_hash
Date: 2022-05-12 14:55:03
Message-ID: 327353.1652367303@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Here, that doesn't seem too likely. You could have a column that
> contains 'tom' and ['tom'] and [['tom']] and [[['tom']]] and so forth
> and they all get mapped onto the same bucket and you're sad. But
> probably not.

Yeah, that might be a more useful way to think about it: is this likely
to cause performance-critical collisions in practice? I agree that
that doesn't seem like a very likely situation, even given that you
might be using json for erratically-structured data.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-05-12 15:37:37 Re: Mark all GUC variable as PGDLLIMPORT
Previous Message vignesh C 2022-05-12 14:35:40 Re: First draft of the PG 15 release notes