pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Julien Rouhaud <rjuju123@gmail.com>
To: Victor Sudakov <vas@sibptus.ru>
Cc: Nikhil Shetty <nikhil.dba04@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Lost replication slots after pg_upgrade.
Date: Tue, 8 Feb 2022 16:45:20 +0800
Message-ID: <20220208084520.hvp3qnwxtfmzq2lr@jrouhaud> (raw)
In-Reply-To: <YgIqlvDg1S9xNNYn@admin.sibptus.ru>
References: <CAFpL5Vws1tJnO8_CeOBO6e2q5K4Zbe4==redhV1yLSekm1U4TQ@mail.gmail.com>
	<Yftm6IwtRKg5QB7P@admin.sibptus.ru>
	<CAFpL5Vx__E4hfvvoCQOmGEtAygowJzto_=sQHUTNbXOpUo1PUQ@mail.gmail.com>
	<YgHkxM8Ocn4F3zWi@admin.sibptus.ru>
	<CAFpL5VxJiFdZ=UKAGNEqNo=U3eSDSFx1uabrrst-GJu2z3zqUg@mail.gmail.com>
	<20220208070404.d2dizlt6nvz2g3og@jrouhaud>
	<YgIqlvDg1S9xNNYn@admin.sibptus.ru>

On Tue, Feb 08, 2022 at 08:32:22AM +0000, Victor Sudakov wrote:
> Julien Rouhaud wrote:
> > 
> > > pg_basebackup takes time for large databases (> 5TB). I feel rsync should
> > > be faster.
> > 
> > Not necessarily.  pg_basebackup will do simple sequential read of all the data,
> > which is probably the fastest thing to do.  rsync will do some extra processing
> > that isn't required in that scenario, so it's likely to be slower (although
> > probably only marginally slower).
> 
> I think Nikhil was going to invoke the rsync black magic as described
> in https://www.postgresql.org/docs/current/pgupgrade.html, not for
> copying the entire PGDATA from the master to standbys. While the rsync
> magic should be hundreds of times faster because only modified files
> will be copied and the majority of files will be just hardlinked, I've
> never felt I have enough skill and luck to undertake this method.

Ah, if that's the case I don't think there's any doubt to have for rsync being
faster.  And this method works just fine if you take care of what you're doing.





view thread (16+ messages)  latest in thread

Message-ID: <20220208084520.hvp3qnwxtfmzq2lr@jrouhaud>
Permalink:  ../20220208084520.hvp3qnwxtfmzq2lr@jrouhaud/
Also on:    postgresql.org/message-id/20220208084520.hvp3qnwxtfmzq2lr@jrouhaud

 · 

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: pgsql-admin@postgresql.org
  Cc: rjuju123@gmail.com, vas@sibptus.ru, nikhil.dba04@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Lost replication slots after pg_upgrade.
  In-Reply-To: <20220208084520.hvp3qnwxtfmzq2lr@jrouhaud>

* 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