Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbTWc-00GpY5-Mo for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Aug 2024 23:23:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sbTWZ-003UQX-Ij for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Aug 2024 23:23:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbTWY-003UQO-Ls for pgsql-hackers@lists.postgresql.org; Tue, 06 Aug 2024 23:23:27 +0000 Received: from relay9-d.mail.gandi.net ([2001:4b98:dc4:8::229]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbTWV-003S3j-FL for pgsql-hackers@lists.postgresql.org; Tue, 06 Aug 2024 23:23:25 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id A32DFFF802; Tue, 6 Aug 2024 23:23:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1722986599; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SqHDVyil0y3pyQBGOPcPLDwckiww+eOUg37iopCu82Q=; b=iO9tQhCNuhks5mRl5t85MSxjj9+e7NNx9Hb3B+vftyIOGSMttQqsqka/o0eha5j6nLGAwq YS6GrWL0/bM5e7ldGFchWDqMmrVc32rj9rVJTTNoVKCbtarZWjyeGSNg3Ng3ljsmM9yeG4 biTfkozMNRnt5kmGNWPArPRGprQWcFIeQYkkew7xeRt9iY1lPPm2MY/Zp/pyBJDKf2cpo+ 48qUPOTk0rQYP0ckhDg+DCxdqOljLxuQkY+XUNOkn3JHy3b4T8D34/DV6jCm9p1MPnz43P e80iSZFurUPd5q+SZAw44q5PVNy8LxfaKxNGon5JG7Me83zJPstrySfN7nLncg== Message-ID: Date: Wed, 7 Aug 2024 01:23:17 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Instability with incremental backup tests (pg_combinebackup, 003_timeline.pl) From: Tomas Vondra To: Michael Paquier , Postgres hackers Cc: Robert Haas References: <962847b5-a6e6-44c2-9b40-789b2a7c29b6@vondra.me> Content-Language: en-US In-Reply-To: <962847b5-a6e6-44c2-9b40-789b2a7c29b6@vondra.me> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-GND-Sasl: tomas@vondra.me List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/6/24 14:53, Tomas Vondra wrote: > On 8/6/24 07:48, Michael Paquier wrote: >> Hi all, >> >> dikkop has reported a failure with the regression tests of pg_combinebackup: >> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dikkop&dt=2024-08-04%2010%3A04%3A51 >> >> That's in the test 003_timeline.pl, from dc212340058b: >> # Failed test 'incremental backup from node1' >> # at t/003_timeline.pl line 43. >> >> The node is extremely slow, so perhaps bumping up the timeout would be >> fine enough in this case (did not spend time analyzing it). I don't >> think that this has been discussed, but perhaps I just missed a >> reference to it and the incremental backup thread is quite large. >> > > Yeah, it's a freebsd running on rpi4, from a USB flash disk, and in my > experience it's much slower than rpi4 running Linux. I'm not sure why is > that, never found a way to make it faster > > The machine already has: > > export PGCTLTIMEOUT=600 > export PG_TEST_TIMEOUT_DEFAULT=600 > > I doubt increasing it further will do the trick. Maybe there's some > other timeout that I should increase? > > FWIW I just moved the buildfarm stuff to a proper SSD disk (still USB, > but hopefully better than the crappy flash disk). > Seems the move to SSD helped a lot - the runs went from ~4h to ~40m. So chances are the instability won't be such a problem. regards -- Tomas Vondra