| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb contains behaviour weirdness |
| Date: | 2014-09-12 18:09:11 |
| Message-ID: | 19057.1410545351@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Geoghegan <pg(at)heroku(dot)com> writes:
> I think this is due to commit 364ddc. That removed the extra step that
> had arrays sorted (and then de-duped) ahead of time, which made arrays
> behave like objects at the top level. I think that this sort + de-dup
> step was mischaracterized as purely a performance thing (possibly by
> me). Basically, JsonbDeepContains() is consistent with the previous
> behavior at the top level, but not the current (inadvertently altered)
> behavior. I think the fix is probably a return to the previous
> behavior. I'll take a closer look.
I'm confused. Are you proposing to return to sort + de-dup of JSON
arrays? Surely that is completely broken. Arrays are ordered.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-09-12 18:14:22 | Re: jsonb contains behaviour weirdness |
| Previous Message | Fabien COELHO | 2014-09-12 17:59:48 | Re: pgbench throttling latency limit |