| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Junwang Zhao <zhjwpku(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: a potential typo in comments of pg_parse_json |
| Date: | 2024-07-08 13:16:33 |
| Message-ID: | CA+HiwqFnRiu=NoRvw_NpmJgsj3HW+qN_whPB+i0bGyTH2+86Qw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 8, 2024 at 5:25 PM Junwang Zhao <zhjwpku(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-07-08 13:21:37 | Re: Injection point locking |
| Previous Message | Amit Langote | 2024-07-08 12:57:00 | Re: Doc Rework: Section 9.16.13 SQL/JSON Query Functions |