Re: [PATCH] Optimize json_lex_string by batching character copying

From: Jelte Fennema <Jelte(dot)Fennema(at)microsoft(dot)com>
To: Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Optimize json_lex_string by batching character copying
Date: 2022-08-29 10:47:28
Message-ID: HE1PR8303MB0075DB9ABBE2DDC6330A33C1F7769@HE1PR8303MB0075.EURPRD83.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I wonder why copyable_characters_length is not reset after flushing.

It's not necessary because of the break statement right after. But this part
of the code was refactored away in John's improved patch that's actually
merged: 
https://github.com/postgres/postgres/commit/3838fa269c15706df2b85ce2d6af8aacd5611655 

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2022-08-29 10:49:46 Re: use ARM intrinsics in pg_lfind32() where available
Previous Message Thomas Munro 2022-08-29 10:21:30 Re: logical decoding and replication of sequences