Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gVoc6-0008CW-OD for pgsql-hackers@arkaria.postgresql.org; Sun, 09 Dec 2018 02:14:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gVoc3-0008Nk-Ex for pgsql-hackers@arkaria.postgresql.org; Sun, 09 Dec 2018 02:14:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gVoc1-0008Nc-OM for pgsql-hackers@lists.postgresql.org; Sun, 09 Dec 2018 02:14:31 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gVobs-00067W-LJ for pgsql-hackers@postgresql.org; Sun, 09 Dec 2018 02:14:28 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id ACE6F3E9; Sat, 8 Dec 2018 21:14:17 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sat, 08 Dec 2018 21:14:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=rIfj9TRsUp4TsAjAWrcF2BRnHoq KPO61qdWXevufQSQ=; b=D+RiPQ79PauHuZ+Q8DCWfyzX526eluv/F41T/nwA1vV jtVR3PV/CWj1bObuszMkKcvQZEvQNf41zVfXiFZYAWwcwNBsZ71PF8Gkv8ZaOGHu 5ptbOVf/teahPJ+WIRFsVIauLB+w4nVDSHHHPfIEygbHZnMMJ4R1N2xKW849QcaF TsxpPETCyO6wFtG32pTYO34gIwfgR55bzcNZbCzV9aXIDnr1BOLTKse/U8m5cxoH nsUwbEF7aMapK8wci5ciKTSGCrEwluf6vXF2jYDbiwxe7ly/8U+HMWlIS1iQpc4Y 5+i3gWjVrUpx6ksndT04dCKX6QjAxhr31HqpBUOKqcQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=rIfj9T RsUp4TsAjAWrcF2BRnHoqKPO61qdWXevufQSQ=; b=s4o1HB+it9dyq3Mvm+iIdp kdXqotZ7G8hF7z5ZsMYjVWrNn0ZIDJLm8XII8lfak55luCEOslL0y7Uuk+27SQFt CyDDO09fWF+DMZ7bz/QwLucHJZpkqCynlpkrlke0NWS4PhILTymRVScupBUVKs97 24Nit1es2JYjxP0/8XAkQu3j/OB8Ub1lf97EJQvEEQ24pggIV7zFlaEW+Szpb5zk qjFHnnIXogc3Ax0+ZQqG1m51zUItURauwovw7YlMjabx8jj7PPrsJhfd0t5WDMBR PzgQtw2T93KhslcsdGMn6jFXGAqkN0c9NRLKhHHDUTp5/vVa24TCGcT8p6QilzXg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudegvddgtdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfghrlhcuvffnffculdejtd dmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgt hhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqne cukfhppeduudekrddvgedurddvhedurddukeehnecurfgrrhgrmhepmhgrihhlfhhrohhm pehmihgthhgrvghlsehprghquhhivghrrdighiiinecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from paquier.xyz (mp76f1fbb9.ap.nuro.jp [118.241.251.185]) by mail.messagingengine.com (Postfix) with ESMTPA id 616D51030E; Sat, 8 Dec 2018 21:14:15 -0500 (EST) Date: Sun, 9 Dec 2018 11:14:12 +0900 From: Michael Paquier To: Noah Misch Cc: pgsql-hackers@postgresql.org Subject: Re: Too-short timeouts in test code Message-ID: <20181209021412.GC1833@paquier.xyz> References: <20181209001601.GC2973271@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="xB0nW4MQa6jZONgY" Content-Disposition: inline In-Reply-To: <20181209001601.GC2973271@rfd.leadboat.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --xB0nW4MQa6jZONgY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 08, 2018 at 04:16:01PM -0800, Noah Misch wrote: > The 180s timeout in poll_query_until has been trouble-free since 2a0f89c > introduced it two years ago. I plan to raise the timeouts in question to > 180s, as attached. That's annoying, thanks for tracking those down. > @@ -72,7 +72,7 @@ my $endpos =3D $node_master->safe_psql('postgres', > print "waiting to replay $endpos\n"; > =20 > my $stdout_recv =3D $node_master->pg_recvlogical_upto( > - 'postgres', 'test_slot', $endpos, 10, > + 'postgres', 'test_slot', $endpos, 180, > 'include-xids' =3D> '0', > 'skip-empty-xacts' =3D> '1'); Instead of allowing callers of pg_recvlogical_upto() to define the timeout they want, perhaps it would be better to hardcode the timeout limit within the routine? -- Michael --xB0nW4MQa6jZONgY Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlwMenQACgkQnvQgOdby QH0ECQ//fp7juhA2SHi+Y0eYt0D8u2fqzYt1Qsdx+vlUo6FzW9fbu2xDPtlXTwRT w9hZbr7Il5rbuXawpb4weg5pgHuH76Kcw36Ssy3EP+buhbHwFa1HKkIVpsF7yLTy 9+JIEwNissh/cZhtOanvXjC+lDD34CW4TOKDTASDYbRtWyXXl3ZCgrMtIeRmIljY rFuJXAXV1TPDkeXy9PMzq0WNV9b5GRkcVwefXL7mAKTVhp55QD08E9ZIPTBrt5nR pDO7VUJdcB9IiIlo+AA2IV8l87Lpk4ajNjQOQm/JViolc7TybKQRGaWwd7C8yJVX p4lO8h1WA/+anHqqIxSZpNhLxzMFVmorhJjgHXa0P0yh4RnW5kMUbqwij4Zn7W2B 4X0kim6gMSatpWZbXgWKcyG6rKtCOXQq7PgMkdSg3g6ZTvDmhwx0E4CncyVq9yfW aEhX8NStXUXR/Ktd8UyN4YbwhaPqjs1R8wDOetQUKkpQjDx3KZH+i5kzQidZeYNF r7NGA5jSaDX3HP6YjKVIWmU9jh1APrZZAtkS4q5KUIplnB22YWmsvHlJWXB86+PV toWtk2EJBhwoFThqPC+3XVhlNjOu4ADe9IVKnBYTsTYTrb9iHurMGUcHvCn7/H3e T65Q6gLkn1fJvvHoAqMsFuJ1wnTLDZ3Wp3w6l1YXxfpUuc8c3IA= =Q76V -----END PGP SIGNATURE----- --xB0nW4MQa6jZONgY--