Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1nep44-0001Cz-3z
	for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Apr 2022 02:18:32 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1nep42-0000MX-Sz
	for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Apr 2022 02:18:30 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nep42-0000MM-Jp
	for pgsql-hackers@lists.postgresql.org; Thu, 14 Apr 2022 02:18:30 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nep40-0007AZ-9T
	for pgsql-hackers@lists.postgresql.org; Thu, 14 Apr 2022 02:18:30 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 23E2IMYh1406169;
	Wed, 13 Apr 2022 22:18:22 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Noah Misch <noah@leadboat.com>, Peter Geoghegan <pg@bowt.ie>,
        David Rowley <dgrowleyml@gmail.com>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Intermittent buildfarm failures on wrasse
In-reply-to: <20220414015112.yhruzx3dbjnz4pji@alap3.anarazel.de>
References: 
 <CAApHDvrHtXtDCjbdRLJAKOO6warCd4WELxK9tq0mUz3u1OaLOg@mail.gmail.com>
 <9F59C4BB-3C82-44B0-9B10-4A2CCC3DE552@anarazel.de>
 <CAH2-WzmOJ5YeT1SsBZ7kp2B+EMMVH9RYShornT13oyduEVwKSw@mail.gmail.com>
 <1364997.1649893086@sss.pgh.pa.us>
 <CAH2-WzkUGqFNXhnFRbVG4xfTo3WpapcdRaH4hQSTrNvDgYvYoQ@mail.gmail.com>
 <1365924.1649893883@sss.pgh.pa.us>
 <CAH2-Wzn2Obp90oyZa5HN26rzG8ozzHM3dgkpLcsVzxTR+jK5NQ@mail.gmail.com>
 <1374062.1649896550@sss.pgh.pa.us>
 <20220414010505.s7z24jxrfsjbzz7l@alap3.anarazel.de>
 <1401379.1649899392@sss.pgh.pa.us>
 <20220414015112.yhruzx3dbjnz4pji@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Wed, 13 Apr 2022 18:51:12 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1406167.1649902702.1@sss.pgh.pa.us>
Date: Wed, 13 Apr 2022 22:18:22 -0400
Message-ID: <1406168.1649902702@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/1406168.1649902702%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> Noah, any chance you could enable log_autovacuum_min_duration=0 on
> wrasse?

+1

> Does sparc have wider alignment rules for some types? Perhaps that'd be
> enough to put some tables to be sufficiently larger to trigger parallel
> vacuum?

No, the configure results on wrasse look pretty ordinary:

checking size of void *... 8
checking size of size_t... 8
checking size of long... 8
checking alignment of short... 2
checking alignment of int... 4
checking alignment of long... 8
checking alignment of double... 8

I wondered for a moment about force_parallel_mode, but wrasse doesn't
appear to be setting that, and in any case I'm pretty sure it only
affects plannable statements.

			regards, tom lane