| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <adunstan(at)postgresql(dot)org>, pgbuildfarm(at)rjuju(dot)net |
| Subject: | Re: what's going on with lapwing? |
| Date: | 2025-03-06 21:19:22 |
| Message-ID: | 899724.1741295962@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> The only reason it's not there is that nobody's ever asked for it ;-)
> You can specify an actual list right now instead of a keyword for
> branches_to_build. e.g. "branches_to_build => [qw(REL_13_STABLE
> REL_14_STABLE REL_15_STABLE)]". The only difficulty about this is you
> need to prune the list when a branch goes EOL.
Right; it's that need for manual maintenance that I'd like to
get out from under.
> But we could also build in some keyword type settings too, that would
> interact more sensibly with the server list of branches.
> So we could say something like "branches_to_build =>
> 'UP_TO_REL_15_STABLE'". That would be pretty simple to code for.
WFM.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alena Rybakina | 2025-03-06 21:20:38 | Re: explain analyze rows=%.0f |
| Previous Message | Alena Rybakina | 2025-03-06 21:18:52 | Re: explain analyze rows=%.0f |