On Thu, Jun 23, 2022 at 9:06 PM Andres Freund <and...@anarazel.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
