| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robins Tharakan <tharakan(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Sam James <sam(at)gentoo(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Build failure with GCC 15 (defaults to -std=gnu23) |
| Date: | 2024-12-14 17:04:50 |
| Message-ID: | 1387395.1734195890@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Robins Tharakan <tharakan(at)gmail(dot)com> writes:
> Unrelated, for a slow system my understanding was that it's quite
> inefficient to keep running older
> branches every few minutes (like HEAD does) - so for some of the animals I
> explicitly run older
> branches (for e.g. v13) every few hours, but HEAD runs every few minutes.
> Are you saying it's still a good idea to run all together every few minutes
> (and let older branches
> skip if there's nothing to do)?
Nowadays run_branches' check for whether there's something to do is
cheap enough that it's not worth skipping. So it's recommendable
to just launch that every so often, and not complicate your life
with manual per-branch scheduling.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robins Tharakan | 2024-12-15 07:04:23 | Re: Build failure with GCC 15 (defaults to -std=gnu23) |
| Previous Message | Robins Tharakan | 2024-12-14 10:46:57 | Re: Build failure with GCC 15 (defaults to -std=gnu23) |