Re: a potential typo in comments of pg_parse_json - Mailing list pgsql-hackers

From Amit Langote
Subject Re: a potential typo in comments of pg_parse_json
Date
Msg-id CA+HiwqFnRiu=NoRvw_NpmJgsj3HW+qN_whPB+i0bGyTH2+86Qw@mail.gmail.com
Whole thread Raw
In response to a potential typo in comments of pg_parse_json  (Junwang Zhao <zhjwpku@gmail.com>)
List pgsql-hackers
On Mon, Jul 8, 2024 at 5:25 PM Junwang Zhao <zhjwpku@gmail.com> wrote:
> Not 100% sure, sorry if this doesn't make sense.
>
> --- a/src/common/jsonapi.c
> +++ b/src/common/jsonapi.c
> @@ -514,7 +514,7 @@ freeJsonLexContext(JsonLexContext *lex)
>   *
>   * If FORCE_JSON_PSTACK is defined then the routine will call the non-recursive
>   * JSON parser. This is a useful way to validate that it's doing the right
> - * think at least for non-incremental cases. If this is on we expect to see
> + * thing at least for non-incremental cases. If this is on we expect to see
>   * regression diffs relating to error messages about stack depth, but no
>   * other differences.
>   */

Good catch.  Fixed.


--
Thanks, Amit Langote



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Doc Rework: Section 9.16.13 SQL/JSON Query Functions
Next
From: Heikki Linnakangas
Date:
Subject: Re: Injection point locking