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 ) id 1jMoc0-0005Br-4U for pgsql-bugs@arkaria.postgresql.org; Fri, 10 Apr 2020 08:02:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jMobT-0000Uc-Jt for pgsql-bugs@arkaria.postgresql.org; Fri, 10 Apr 2020 08:01:31 +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 ) id 1jMobT-0000UU-E2 for pgsql-bugs@lists.postgresql.org; Fri, 10 Apr 2020 08:01:31 +0000 Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jMobP-0007j5-Gg for pgsql-bugs@postgresql.org; Fri, 10 Apr 2020 08:01:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com; s=20170201; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Reply-To:Message-ID:Subject:Cc:To:Sender:From:Date: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=G+eES3N36XWP12l/3lBlfEyJZEA+gmRaRKUks1I7v0c=; b=vUvSMoKYv1o7nAMy8nuGx/5IgO 54TrDEXhZxuaH77+TFBvmDYPhnfGrmjwGiebuMqYcZiLyCCseVjyrhDM3V7cwVSULAQLKBjpoZq7H /d48oiFo+73DXKfVZH0rKWovPcrUz1ZBIuSaO4PBb2SZDHg5dP6M6HukNIF6jrux4hxQ=; Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by depesz.com with esmtpa (Exim 4.92) (envelope-from ) id 1jMobK-0006vY-8S; Fri, 10 Apr 2020 10:01:22 +0200 Date: Fri, 10 Apr 2020 10:01:22 +0200 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: Michael Paquier Cc: Victor Yegorov , Andrew Gierth , pgsql-bugs mailing list Subject: Re: Loss of replication after simple misconfiguration Message-ID: <20200410080122.GA23421@depesz.com> Reply-To: depesz@depesz.com References: <20200409140836.GA5990@depesz.com> <878sj4skmj.fsf@news-spur.riddles.org.uk> <20200410041434.GU1606@paquier.xyz> <20200410072651.GA16098@depesz.com> <20200410075932.GY1606@paquier.xyz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20200410075932.GY1606@paquier.xyz> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Apr 10, 2020 at 04:59:32PM +0900, Michael Paquier wrote: > On Fri, Apr 10, 2020 at 09:26:51AM +0200, hubert depesz lubaczewski wrote: > > In our case it was *at least* this scenario: > >=20 > > 1. master and slave both with max_worker_processes and > > track_commit_timestamp off. > > 2. config files get changed on both to include track_commit_timestamp on > > 3. slave gets restarted > > 4. config files get changed on both to include max_worker_processes =3D= 50 > > 5. master gets stopped by "power outage" > > 6. after master re-starts, replication to slave dies. >=20 > Without the standby restarted here, its configuration remains at the > former value of max_worker_processes, which is lower than the setting > of the primary, so it would logically stop in this case if not > restarted once it replays the XLOG_PARAMETER_CHANGE record generated > from the primary. Yes, I know. And this is *precisely* what has happened in at least one case. But I would assume that after restart, standby should be working. Which didn't happen (in at least one case, we had lots of restarts recently, and only ~ 4 cases of replication dying). Best regards, depesz