> -Original Message-
> From: Daniel Gustafsson
> Sent: Monday, 8 March 2021 9:42 AM
> To: Tharakan, Robins
> Cc: pgsql-hack...@postgresql.org
> Subject: RE: [EXTERNAL] pg_upgrade failing for 200+ million Large Objects
>
> CAUTION: This email originated from outside
Original Message-
> From: Peter Eisentraut
> Sent: Monday, 8 March 2021 9:25 PM
> To: Tharakan, Robins ; pgsql-hack...@postgresql.org
> Subject: [EXTERNAL] [UNVERIFIED SENDER] Re: pg_upgrade failing for 200+
> million Large Objects
>
> CAUTION: This email originated from ou
Hi David / Tom,
> David Rowley writes:
> It would be good to have log_autovacuum_min_duration = 0 on this machine for
> a while.
- Have set log_autovacuum_min_duration=0 on parula and a test run came out okay.
- Also added REL_16_STABLE to the branches being tested (in case it matters
here).
> ... in connection with which, I can't help noticing that parula is using a
> very old compiler:
>
> configure: using compiler=gcc (GCC) 7.3.1 20180712 (Red Hat 7.3.1-17)
>
> From some quick checking around, that would have to be near the beginning of
> aarch64
> support in RHEL (Fedora hadn't p
> I've now switched to GCC v13.2 and triggered a run. Let's see if the tests
> stabilize now.
So although HEAD ran fine, but I saw multiple failures (v12, v13, v16) all of
which passed on subsequent-tries,
of which some were even"signal 6: Aborted".
FWIW, I compiled gcc v13.2 (default options)
