Re: Adding argument names to aggregate functions - Mailing list pgsql-hackers

From Jim Jones
Subject Re: Adding argument names to aggregate functions
Date
Msg-id cd7c78aa-ec48-3e40-a7f9-edf77ff5742e@uni-muenster.de
Whole thread Raw
In response to Re: Adding argument names to aggregate functions  (Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>)
Responses Re: Adding argument names to aggregate functions  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
On 18.04.23 12:27, Dagfinn Ilmari Mannsåker wrote:
> Link to the actual job:
> https://cirrus-ci.com/task/5881376021413888
>
> The failure was:
>
> [09:54:38.727] 216/262 postgresql:recovery / recovery/031_recovery_conflict ERROR 198.73s exit status 60
>
> Looking at its log:
>
>
https://api.cirrus-ci.com/v1/artifact/task/5881376021413888/testrun/build/testrun/recovery/031_recovery_conflict/log/regress_log_031_recovery_conflict
>
> we see:
>
> timed out waiting for match: (?^:User was holding a relation lock for too long) at
/Users/admin/pgsql/src/test/recovery/t/031_recovery_conflict.plline 311.
 
>
> That looks indeed completely unrelated to this patch.

Yes, that's what I suspected. The patch passes all tests now :)

I've marked the CF entry as "Ready for Committer".

Jim




pgsql-hackers by date:

Previous
From: Dagfinn Ilmari Mannsåker
Date:
Subject: Re: Adding argument names to aggregate functions
Next
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] Add `verify-system` sslmode to use system CA pool for server cert