pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Anastasia Lubennikova <lubennikovaav@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: A test for replay of regression tests
Date: Tue, 01 Feb 2022 21:33:10 -0500
Message-ID: <1048961.1643769190@sss.pgh.pa.us> (raw)
In-Reply-To: <C5105396-9938-4CEE-8711-94481F311102@anarazel.de>
References: <YbmsZbEO1QGMymNF@paquier.xyz>
	<YbqG0DsKGRBnY/4t@paquier.xyz>
	<CA+hUKGK-+mg6RWiDu0JudF6jWeL5+gPmi8EKUm1eAzmdbwiE_A@mail.gmail.com>
	<CA+hUKG+GBC-6QhOKt6Y7ccrXSjbRHB7Di295=0rAGhE7a7hSrQ@mail.gmail.com>
	<CA+hUKGLneD+q+E7upHGwn41KGvbxhsKbJ+M-y9nvv7_Xjv8Qog@mail.gmail.com>
	<20220114234947.av4kkhuj7netsy5r@alap3.anarazel.de>
	<CA+hUKG+yxxnFWvp4h_HgJvptQ2uKE4aKtDd7e5nmr61Soe6a2Q@mail.gmail.com>
	<20220121194827.7eau4ulhrfol3npd@alap3.anarazel.de>
	<CA+hUKGK65xVqNgsSPyrr2LEwtfUN=GfEuQ868hTC-mu0bFG42A@mail.gmail.com>
	<CA+hUKG+1=MpM2aXOHhXE9myBqMsgV4N0fOTgCqubZZ_mXgRuQg@mail.gmail.com>
	<20220202011402.e7t3hu3jusalr32h@alap3.anarazel.de>
	<CA+hUKGK6mG8-6VieDm3sz2yzqMqw7j_=ag=_XmKLKsS-hG6KQw@mail.gmail.com>
	<1046818.1643767884@sss.pgh.pa.us>
	<C5105396-9938-4CEE-8711-94481F311102@anarazel.de>

Andres Freund <andres@anarazel.de> writes:
> It's not surprising that pg_dump takes 30s on that old a machine. But more than 2min still surprised me. Is that really do be expected?

In the previous buildfarm run, that dump took just under 31s:

2022-01-31 14:21:10.358 EST [19325:1] [unknown] LOG:  connection received: host=[local]
2022-01-31 14:21:10.367 EST [19325:2] [unknown] LOG:  connection authorized: user=buildfarm database=regression application_name=027_stream_regress.pl
...
2022-01-31 14:21:41.139 EST [19325:2663] 027_stream_regress.pl LOG:  disconnection: session time: 0:00:30.782 user=buildfarm database=regression host=[local]

In the failing run, we have:

2022-02-01 04:48:37.757 EST [3683:1] [unknown] LOG:  connection received: host=[local]
2022-02-01 04:48:37.767 EST [3683:2] [unknown] LOG:  connection authorized: user=buildfarm database=regression application_name=027_stream_regress.pl
...
2022-02-01 04:49:09.719 EST [3683:2584] 027_stream_regress.pl LOG:  statement: COPY public.tenk1 (unique1, unique2, two, four, ten, twenty, hundred, thousand, twothousand, fivethous, tenthous, odd, even, stringu1, stringu2, string4) TO stdout;
2022-02-01 04:49:09.881 EST [3683:2585] 027_stream_regress.pl ERROR:  canceling statement due to conflict with recovery
2022-02-01 04:49:09.881 EST [3683:2586] 027_stream_regress.pl DETAIL:  User query might have needed to see row versions that must be removed.
2022-02-01 04:49:09.881 EST [3683:2587] 027_stream_regress.pl STATEMENT:  COPY public.tenk1 (unique1, unique2, two, four, ten, twenty, hundred, thousand, twothousand, fivethous, tenthous, odd, even, stringu1, stringu2, string4) TO stdout;
2022-02-01 04:49:09.889 EST [3685:1] [unknown] LOG:  connection received: host=[local]
2022-02-01 04:49:09.905 EST [3683:2588] 027_stream_regress.pl LOG:  could not send data to client: Broken pipe
2022-02-01 04:49:09.905 EST [3683:2589] 027_stream_regress.pl ERROR:  canceling statement due to conflict with recovery
2022-02-01 04:49:09.905 EST [3683:2590] 027_stream_regress.pl DETAIL:  User query might have needed to see row versions that must be removed.
2022-02-01 04:49:09.906 EST [3683:2591] 027_stream_regress.pl FATAL:  connection to client lost
2022-02-01 04:49:09.935 EST [3683:2592] 027_stream_regress.pl LOG:  disconnection: session time: 0:00:32.179 user=buildfarm database=regression host=[local]

That's only a little over 30s.  Where are you getting 2m from?

			regards, tom lane





view thread (82+ messages)  latest in thread

Message-ID: <1048961.1643769190@sss.pgh.pa.us>
Permalink:  ../1048961.1643769190@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1048961.1643769190@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-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, thomas.munro@gmail.com, michael@paquier.xyz, andrew@dunslane.net, lubennikovaav@gmail.com
  Subject: Re: A test for replay of regression tests
  In-Reply-To: <1048961.1643769190@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