Peter Geoghegan <p...@heroku.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers