pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robins Tharakan <tharakan@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Andres Freund <andres@anarazel.de>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>
Cc: Sam James <sam@gentoo.org>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Build failure with GCC 15 (defaults to -std=gnu23)
Date: Sat, 14 Dec 2024 12:04:50 -0500
Message-ID: <1387395.1734195890@sss.pgh.pa.us> (raw)
In-Reply-To: <CAEP4nAzNb=ikYY6k8a0V2XP-M-HXga6Wf2hVbr7JAY1Aots-1Q@mail.gmail.com>
References: <485f5982-18c5-4210-9c7d-7c05453f7033@eisentraut.org>
	<CA+hUKGL0LWK7hVO9r2eb3hFDBptZByOkAKGAjXKJ5mqd9hs_fA@mail.gmail.com>
	<1447160.1732565223@sss.pgh.pa.us>
	<CA+hUKG+5ErSyS2+rqx0bvKAWadP9NQBOsUgZVpz74ZB0DA=nJw@mail.gmail.com>
	<1578470.1732587191@sss.pgh.pa.us>
	<CA+hUKGJ4HEntEJkpqinyaLn3AfXMvCirWk0n2H4LWDxSSGh-Dw@mail.gmail.com>
	<CA+hUKG+y2q0dP=g=bbkAWD66unrSKsQEc29ERvA_6fTC3b954Q@mail.gmail.com>
	<1897695.1732732104@sss.pgh.pa.us>
	<eu34f6armrlbq7cdai3dy45576h3qybme47uxens4cowpghzqe@52owmagijfiu>
	<2gao2zapw2dumahxgma4t3c6cquy4vnjs5bt4yvduexpywwm2m@3uhxxc63xvlq>
	<CAEP4nAw4UHSgcHFL7Rsub0nCHW=6ZCrpiuBUT_dV5+4apS=Q5Q@mail.gmail.com>
	<494522.1732894313@sss.pgh.pa.us>
	<CAEP4nAyRfWZ8T8xzNHHy4p8kLCrXAAY7Hbs2_P8YCOJiu=6SCA@mail.gmail.com>
	<970389.1734052913@sss.pgh.pa.us>
	<CAEP4nAyOKW+CLHrFDHw1e6fjEG+urL2x1DSeFiU8vnaGsOrV1g@mail.gmail.com>
	<CAEP4nAzOaY0PR-7_t6aN-Dwq6vZzO3i0JAAx2BBRUzy3LwtNGw@mail.gmail.com>
	<CAEP4nAxMtdyj7xtrf_fPNj8qU0bprOR=fDiCc154_UhQyUZ5cA@mail.gmail.co! m>
	<8877ae08-5dcd-45bf-8475-c6d5a5200346@dunslane.net>
	<CAEP4nAzNb=ikYY6k8a0V2XP-M-HXga6Wf2hVbr7JAY1Aots-1Q@mail.gmail.com>

Robins Tharakan <tharakan@gmail.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





view thread (42+ messages)  latest in thread

Message-ID: <1387395.1734195890@sss.pgh.pa.us>
Permalink:  ../1387395.1734195890@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1387395.1734195890@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, tharakan@gmail.com, andrew@dunslane.net, andres@anarazel.de, thomas.munro@gmail.com, peter@eisentraut.org, sam@gentoo.org, pgsql-bugs@lists.postgresql.org
  Subject: Re: Build failure with GCC 15 (defaults to -std=gnu23)
  In-Reply-To: <1387395.1734195890@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox