| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: CI and test improvements |
| Date: | 2024-04-11 01:12:10 |
| Message-ID: | Zhc46l9Vu3jsYs2x@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 08, 2024 at 05:54:10PM +0300, Andrey M. Borodin wrote:
> Justin, Peter, I can't determine actual status of the CF entry
> [0]. May I ask someone of you to move patch to next CF or close as
> committed?
0002 is the only thing committed as of 21a71648d39f.
I can see the value in 0001, but the implementation feels awkward.
0003 is wanted.
I am personally not sure about 0004 to upload doc artifacts.
Similarly.
0005 can already be done with a few clicks on the CI, and the previous
run may not be the only one that matters.
0006 makes the doc check phase more complex.
In all that, 0003 is something that we should move on with, at least.
Moving this entry to the next CF makes sense to me now, to give more
time to the other patches, and there's value to be extracted at quick
glance.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2024-04-11 01:32:52 | Re: Improve eviction algorithm in ReorderBuffer |
| Previous Message | Michael Paquier | 2024-04-11 01:01:23 | Re: Improve WALRead() to suck data directly from WAL buffers when possible |