From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Amit Langote <amitlangote09@gmail.com>
Cc: Amit Langote <amitlan@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add basic JSON_TABLE() functionality
Date: Thu, 04 Apr 2024 11:26:47 -0400
Message-ID: <601996.1712244407@sss.pgh.pa.us> (raw)
In-Reply-To: <49c3a0cc-2998-4e25-8bc3-e70b3cba87eb@dunslane.net>
References: <E1rsL9y-000S60-Pn@gemulon.postgresql.org>
<f8402aef-c66c-4207-992c-fdee5e59c612@dunslane.net>
<CA+HiwqF8KeHyoNi8TM-fUuE_002GYANbM55ybqEWi5QRinX5YQ@mail.gmail.com>
<49c3a0cc-2998-4e25-8bc3-e70b3cba87eb@dunslane.net>
Andrew Dunstan <andrew@dunslane.net> writes:
> On 2024-04-04 Th 09:20, Amit Langote wrote:
>> I don't get that WARNING here, but I remember seeing it at one point,
>> which I am supposed to have fixed.
>>
>> Can you please share more details about where you're seeing it?
> It's with a meson build:
I see it with autoconf builds too, both on RHEL8 and macOS.
Looking at parse.pl, I guess it's probably triggered by some
unconventional use of ERRCODE_FEATURE_NOT_SUPPORTED in your
gram.y changes.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, amitlangote09@gmail.com, amitlan@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add basic JSON_TABLE() functionality
In-Reply-To: <601996.1712244407@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox