From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Jelte Fennema <me(at)jeltef(dot)nl>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, kevinvan(at)shift(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP Patch: Add a function that returns binary JSONB as a bytea |
Date: | 2022-06-24 07:33:00 |
Message-ID: | CAFBsxsGb3Uq0iM5bukgTHcKBbmaC+7Vk2+uyyNAQYWjmnpwdzQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 23, 2022 at 9:06 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> It looks like there's quite a bit of low hanging fruits to optimize...
Yeah, if escapes and control characters are rare, adding an SSE2 fast
path would give a boost to json_lex_string: check 16 bytes at a time
for those chars (plus the ending double-quote). We can also shave a
few percent by having pg_utf8_verifystr use SSE2 for the ascii path. I
can look into this.
--
John Naylor
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Önder Kalacı | 2022-06-24 08:09:06 | Re: Postgres do not allow to create many tables with more than 63-symbols prefix |
Previous Message | Noah Misch | 2022-06-24 05:45:40 | Re: Postgres perl module namespace |