Re: [PATCH] Optimize json_lex_string by batching character copying - Mailing list pgsql-hackers

From Jelte Fennema
Subject Re: [PATCH] Optimize json_lex_string by batching character copying
Date
Msg-id HE1PR8303MB0075DB9ABBE2DDC6330A33C1F7769@HE1PR8303MB0075.EURPRD83.prod.outlook.com
Whole thread Raw
In response to Re: [PATCH] Optimize json_lex_string by batching character copying  (Zhihong Yu <zyu@yugabyte.com>)
List 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 



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: logical decoding and replication of sequences
Next
From: John Naylor
Date:
Subject: Re: use ARM intrinsics in pg_lfind32() where available