Re: duplicate line in ExecEvalJsonCoercionFinish - Mailing list pgsql-hackers

From Amit Langote
Subject Re: duplicate line in ExecEvalJsonCoercionFinish
Date
Msg-id CA+HiwqGef+RQYF+9au37faCyEXNA4sfoCkHpH9wb_yRQEcvjcw@mail.gmail.com
Whole thread Raw
In response to Re: duplicate line in ExecEvalJsonCoercionFinish  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
On Thu, Jul 17, 2025 at 12:03 PM Amit Langote <amitlangote09@gmail.com> wrote:
> On Thu, Jul 17, 2025 at 10:01 AM Richard Guo <guofenglinux@gmail.com> wrote:
> > On Thu, Jul 17, 2025 at 9:52 AM Tender Wang <tndrwang@gmail.com> wrote:
> > > jian he <jian.universality@gmail.com> 于2025年7月17日周四 07:39写道:
> > >> ExecEvalJsonCoercionFinish duplicate line:
> > >>         jsestate->escontext.error_occurred = false;
> > >>         jsestate->escontext.error_occurred = false;
> >
> > > Good catch.  It was introduced by this commit 231b7d670b21.
> > > Add Amit to the cc list.
> >
> > Nice catch!  The two duplicate statements were introduced in separate
> > commits; looks like a copy-paste oversight in the later one.
>
> Oops, you're right -- I must have copy-pasted without noticing the
> duplicate. Thanks Jian for catching that.  Will fix.

Done.  Thanks all.

--
Thanks, Amit Langote



pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: Log prefix missing for subscriber log messages received from publisher
Next
From: Laurenz Albe
Date:
Subject: Re: Fix PQport to never return NULL if the connection is valid