Re: pgsql: Common SQL/JSON clauses - Mailing list pgsql-committers

From Andrew Dunstan
Subject Re: pgsql: Common SQL/JSON clauses
Date
Msg-id 9cc70374-e7bf-d84a-71e6-dac97eb956cc@dunslane.net
Whole thread Raw
In response to Re: pgsql: Common SQL/JSON clauses  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On 3/22/22 20:08, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> On 3/22/22 18:33, Andres Freund wrote:
>>> This currently triggers a number of warnings. I assume that's because of the
>>> following patches not being there yet? How far out are those?
>> Tomorrow, with the SQL/JSON constructors patch should resolve it. So
>> roughly 24 hours. It's not his fault but this happened because Alvaro
>> asked me to stagger the commits.
> Sounds like all you have to do is merge this commit with the next
> one in the series?  Might as well do it if so.  But please don't
> push something that generates warnings.
>
>             



Yes, mea maxima culpa. I am working on a newer development machine than
the one I have used for years and I forgot to add check_warnings to the
test setup. That's remedied now.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-committers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: pgsql: Allow pgbench to retry in some cases.
Next
From: Robert Haas
Date:
Subject: pgsql: Replace BASE_BACKUP COMPRESSION_LEVEL option with COMPRESSION_DE