Re: A compiling warning in jsonb_populate_record_valid

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Richard Guo <guofenglinux(at)gmail(dot)com>
Subject: Re: A compiling warning in jsonb_populate_record_valid
Date: 2024-01-25 15:28:06
Message-ID: CA+HiwqHqHnJ-qUkbj4G80Y32ZAM+XwhAv1PD7aifhtskj8-5AA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 26, 2024 at 0:15 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> > On Thu, Jan 25, 2024 at 23:57 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> -1 please. We should not break that abstraction for the sake
> >> of ignorable warnings on ancient compilers.
>
> > Ignoring the warning was my 1st thought too, because an old discussion I
> > found about the warning was too old (2011). The style I adopted in my
> > “fix” is used in a few other places too, so I thought I might as well
> > go for it.
>
> Oh, well maybe I'm missing some context. What comparable places did
> you see?

Sorry, not on my computer right now so can’t paste any code, but I was able
to find a couple of functions (using Google ;) that refer to error_occurred
directly for one reason or another:

process_integer_literal(),
xml_is_document()

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2024-01-25 15:40:26 Re: More new SQL/JSON item methods
Previous Message Japin Li 2024-01-25 15:22:41 Re: Unnecessary smgropen in {heapam_relation,index}_copy_data?