Re: Logical replication stops dropping used initial-sync replication slots

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: pgsql-bugs mailing list <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Logical replication stops dropping used initial-sync replication slots
Date: 2022-03-22 11:26:46
Message-ID: 20220322112646.GA14817@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Mar 22, 2022 at 12:32:41PM +0530, vignesh C wrote:
> > That wouldn't do me any good. The server I'm trying to upgrade now is
> > test bench to make sure that I can upgrade using logical replication *at
> > all*.
> > Once I will have verified that I can, I have couple hundred servers to
> > upgrade, that will have concurrent access all the time.
> Is it possible to get a reproducible test or a script for this problem?

Well, given that we're talking about 38GB database with 60k tables
i find that unlikely.

But I'll try if I can figure out a way to replicate the problem with
something that is shareable.

depesz

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Prajna Shetty 2022-03-22 12:57:10 Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
Previous Message vignesh C 2022-03-22 07:02:41 Re: Logical replication stops dropping used initial-sync replication slots