pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Thomas Munro <tmunro@postgresql.org>
Cc: pgsql-committers <pgsql-committers@lists.postgresql.org>
Subject: Re: pgsql: Test replay of regression tests, attempt II.
Date: Tue, 18 Jan 2022 12:40:12 -0800
Message-ID: <20220118204012.qpfas4fmvc55g4ei@alap3.anarazel.de> (raw)
In-Reply-To: <374643.1642536944@sss.pgh.pa.us>
References: <E1n9Io8-0007At-FQ@gemulon.postgresql.org>
	<YeUUiruW+mqNNGIG@paquier.xyz>
	<20220117203746.oj43254j5jurbneu@alap3.anarazel.de>
	<CA+hUKGLT2UL5_JhmBzUgkdyKfc=5J-gJSQJLysMs4rqLUKLAzw@mail.gmail.com>
	<CA+hUKGJDrokTTT3fAEESHiW5TmwxkkJGqe8bR-VFjpg4+hK+fQ@mail.gmail.com>
	<374643.1642536944@sss.pgh.pa.us>

On 2022-01-18 15:15:44 -0500, Tom Lane wrote:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rorqual&dt=2022-01-18%2019%3A50%3A57
> 
> That reloptions test has been there awhile, and we weren't seeing
> issues with it before.  What about the replication environment
> would cause VACUUM to behave differently?  Maybe it thinks there
> are non-removable tuples because the walsender is holding back
> global xmin?

hot_standby_feedback isn't enabled, so it shouldn't...

I wonder if it's just a question of the different configuration used by
Cluster.pm, rather than the fact that a replica is actually connected.

Locally I see the following additions to the configuration for the primary in
027_stream_regres.pl

  fsync = off
  restart_after_crash = off
  log_line_prefix = '%m [%p] %q%a '
  log_statement = all
  log_replication_commands = on
  wal_retrieve_retry_interval = '500ms'
  stats_temp_directory = 'pg_stat_tmp'
  wal_level = replica
  max_wal_senders = 10
  max_replication_slots = 10
  wal_log_hints = on
  hot_standby = on
  shared_buffers = 1MB
  max_connections 25
  max_wal_size = 128MB
  port = 63698
  unix_socket_directories = '/tmp/098ygO1bAF'
  listen_addresses = ''
  max_prepared_transactions = 10

That's an extremely small shared_buffers for running the regression tests, it'd not
be surprising if that provoked problems we don't otherwise see. Perhaps VACUUM
ends up skipping over a page because of page contention?

Also, it's odd that there's "max_connections 25" without an equal sign. I'd
kind of expected that to cause an error....

Greetings,

Andres Freund





view thread (18+ messages)  latest in thread

Message-ID: <20220118204012.qpfas4fmvc55g4ei@alap3.anarazel.de>
Permalink:  ../20220118204012.qpfas4fmvc55g4ei@alap3.anarazel.de/
Also on:    postgresql.org/message-id/20220118204012.qpfas4fmvc55g4ei@alap3.anarazel.de

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: andres@anarazel.de, tgl@sss.pgh.pa.us, thomas.munro@gmail.com, michael@paquier.xyz, tmunro@postgresql.org
  Subject: Re: pgsql: Test replay of regression tests, attempt II.
  In-Reply-To: <20220118204012.qpfas4fmvc55g4ei@alap3.anarazel.de>
  References: <E1n9Io8-0007At-FQ@gemulon.postgresql.org> <YeUUiruW+mqNNGIG@paquier.xyz> <20220117203746.oj43254j5jurbneu@alap3.anarazel.de> <CA+hUKGLT2UL5_JhmBzUgkdyKfc=5J-gJSQJLysMs4rqLUKLAzw@mail.gmail.com> <CA+hUKGJDrokTTT3fAEESHiW5TmwxkkJGqe8bR-VFjpg4+hK+fQ@mail.gmail.com> <374643.1642536944@sss.pgh.pa.us> <20220118204012.qpfas4fmvc55g4ei@alap3.anarazel.de>

* 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