From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Paul Jungwirth <pj(at)illuminatedcomputing(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com> |
Subject: | Re: SQL:2011 application time |
Date: | 2025-02-05 13:37:21 |
Message-ID: | 50a1d589-4502-459f-8ce7-4e666684f87e@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 29.01.25 07:34, Paul Jungwirth wrote:
> Is it possible to commit an RI_PLAN_NO_ACTION addition and see if that
> makes the buildfarm failures go away? Here is a proposed patch for that
> (v48.1). I would understand if this is too questionable a practice---but
> it would be nice to get sufficient test exposure to see if it makes a
> difference. Since I still haven't reproduced this locally (despite
> running continuously for almost a week), it's not an experiment I can do
> myself. If it *does* make the failures go away, then it suggests there
> is still some latent problem somewhere.
I'm tempted to give this a try. But the cfbot is currently in a bit of
a mess, so I'll wait until that is clean again so that we can have a
usable baseline to work against.
From | Date | Subject | |
---|---|---|---|
Next Message | Alexandra Wang | 2025-02-05 13:39:15 | Re: SQL:2023 JSON simplified accessor support |
Previous Message | John Naylor | 2025-02-05 13:34:59 | Sort functions with specialized comparators |