public inbox for [email protected]
help / color / mirror / Atom feedFrom: Koen De Groote <[email protected]>
To: Adrian Klaver <[email protected]>
Cc: PostgreSQL General <[email protected]>
Subject: Re: Questions on logical replication
Date: Sat, 8 Jun 2024 19:40:50 +0200
Message-ID: <CAGbX52GF=n7-vi5VnfnMXKkf=CfbX_nAgmy3=eezLU6XWXqjfw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAGbX52FxL9eR=jmS3ACgRC=tEm=xj_xMmFoOxO+wVA+oURW=kA@mail.gmail.com>
<[email protected]>
<CAGbX52HTgb2jYYO5eVDu=xB5-bjAra+34=AUFg4Xk0NpCRjnyg@mail.gmail.com>
<[email protected]>
<CAGbX52EMG+d-BR5SzDP+rQsrdxT32=CXD5XCT2YCmkTpr3jesw@mail.gmail.com>
<[email protected]>
What I'm trying to do is upgrade a PG11 database to PG16, using logical
replication.
The PG11 has an active and a standby, there are a handful of databases. On
particular one has a few tables just over 100GB, then a few 100 tables near
1GB.
What I'd do is start a publication with no tables and add them 1 at a time,
refreshing subscription each time.
This might take a long time, so my main questions relate to potential
network issues or various situations where the instance receiving the
logical replication, suddenly stop being able to receive.
Resyncing, and the effects of WAL buildup, are my main concern.
Accidentally sent a mail to only your email, sorry for that.
Regards,
Koen De Groote
On Fri, Jun 7, 2024 at 5:15 PM Adrian Klaver <[email protected]>
wrote:
> On 6/6/24 15:19, Koen De Groote wrote:
> > I'll give them a read, though it might take a few weekends
> >
> > Meanwhile, this seems to be what I'm looking for:
> >
> > From
> >
> https://www.postgresql.org/docs/current/warm-standby.html#STREAMING-REPLICATION-SLOTS
> <
> https://www.postgresql.org/docs/current/warm-standby.html#STREAMING-REPLICATION-SLOTS
> >
> >
> > " Replication slots provide an automated way to ensure that the primary
> > does not remove WAL segments until they have been received by all
> > standbys, and that the primary does not remove rows which could cause a
> > recovery conflict
> > <
> https://www.postgresql.org/docs/current/hot-standby.html#HOT-STANDBY-CONFLICT;
> even when the standby is disconnected."
> >
> > I'm reading that as: "if there is a replication slot, if the standby is
> > disconnected, WAL is kept"
> >
> > And if we know WAL is kept in the "pg_wal" directory, that sounds like
> > it could slowly but surely fill up disk space.
> >
> >
> > But again, I'll give them a read. I've read all of logical replication
> > already, and I feel like I didn't get my answer there.
>
> It would be a good idea to provide an a fairly specific outline of what
> you are trying to achieve, then it would be easier for folks to offer
> suggestions on what to do or not to do.
>
> >
> > Thanks for the help
> >
> >
> > Regards,
> > Koen De Groote
>
> --
> Adrian Klaver
> [email protected]
>
>
view thread (16+ messages) latest in thread
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Questions on logical replication
In-Reply-To: <CAGbX52GF=n7-vi5VnfnMXKkf=CfbX_nAgmy3=eezLU6XWXqjfw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox