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 1nZAXp-0002T6-Ep for pgsql-bugs@arkaria.postgresql.org; Tue, 29 Mar 2022 12:01:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nZAXn-0007Uj-9E for pgsql-bugs@arkaria.postgresql.org; Tue, 29 Mar 2022 12:01:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nZAXm-0007Ua-UN for pgsql-bugs@lists.postgresql.org; Tue, 29 Mar 2022 12:01:51 +0000 Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nZAXg-0004c0-Jc for pgsql-bugs@postgresql.org; Tue, 29 Mar 2022 12:01:49 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com; s=20170201; h=In-Reply-To:Content-Type:MIME-Version:References:Reply-To: Message-ID:Subject:Cc:To:Sender:From:Date:Content-Transfer-Encoding: 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=Up9PRcURJ566aHc9Gkg9RqOXMnD/Syjb8R6ibY4XWI8=; b=Yl75wyzJ2osFCf8wInRVwR6ZF7 RirmFGzRw1FSAvWfKLGrLkEN1EocgK/I9JpetadowFDnd3PFoq3H80kAI84tytk1xTHmo+DVTkUu+ J776eGTdUm5vV5jfjBkUqJr2UpdYWLtH3PNGYXsz+1VgRZkJbE8UisTcoqdZd6gM/LTc=; Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by depesz.com with esmtpa (Exim 4.92) (envelope-from ) id 1nZAXd-0008NQ-7i; Tue, 29 Mar 2022 14:01:41 +0200 Date: Tue, 29 Mar 2022 14:01:41 +0200 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: Amit Kapila Cc: vignesh C , pgsql-bugs mailing list Subject: Re: Logical replication stops dropping used initial-sync replication slots Message-ID: <20220329120140.GA29363@depesz.com> Reply-To: depesz@depesz.com References: <20220317142426.GA727@depesz.com> <20220318122758.GA25022@depesz.com> <20220321144341.GA27089@depesz.com> <20220322034847.GA15952@depesz.com> <20220322112646.GA14817@depesz.com> <20220325083856.GA26455@depesz.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Mar 29, 2022 at 04:57:42PM +0530, Amit Kapila wrote: > What was your setting for max_logical_replication_workers? It should 4 on source, and 50 on replica. That could be related. Should I increase this on source? > be more than max_sync_workers_per_subscription as that is taken from > the pool of max_logical_replication_workers. One possible reason for The thing is that, in next tests, it seemed to *usually* work. And break just sometimes. > It is good if you are able to proceed but we might get some clue about > the problem you are seeing if you can show subscriber-side logs. Will keep that in mind. The boxes I was testing it are gone, but if the problem will resurface, I'll make the logs available. Best regards, depesz