pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Dirk Krautschick <dirk.krautschick@googlemail.com>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: pg_repack vs. running logical/physical replication
Date: Mon, 29 Jan 2024 15:56:13 +0100
Message-ID: <e8a8d645-3ac2-4673-a484-96c0dfb47bea@googlemail.com> (raw)
In-Reply-To: <CANzqJaB7sWG9PKJ3-=PXMwLRJEg9SNKmLcE_VxkBe-BxF=ijuQ@mail.gmail.com>
References: <CANzqJaAvhK+82KyC=NJ6HGi3VhwHibSUAH2+b2T-3w9Ct4HbXQ@mail.gmail.com>
	<CA+427g9yfibEe62upmOnW7On6ixwvQbXXiLLPwT8vKAQ9p3bYQ@mail.gmail.com>
	<CAAo1mbkFD7yAARhf-oLf4ZuGSr3Xdi8-nYO=whAweKWTeTPVkg@mail.gmail.com>
	<CANzqJaB7sWG9PKJ3-=PXMwLRJEg9SNKmLcE_VxkBe-BxF=ijuQ@mail.gmail.com>

Hi,


is there any good reason to cut of logical and/or physical replication 
for the time pg_repack (please no discussion about pg_repack at all, 
customer request, his idea, his strict wish) is running? I am not so 
deep into how pg_repack is running things but as the docs are saying it 
could affect hard at least the publications for logrep. Haven't tested 
it yet and just hopeing for a quick answer here :-)


Thanks and best regards


Dirk






view thread (4+ messages)  latest in thread

Message-ID: <e8a8d645-3ac2-4673-a484-96c0dfb47bea@googlemail.com>
Permalink:  ../e8a8d645-3ac2-4673-a484-96c0dfb47bea@googlemail.com/
Also on:    postgresql.org/message-id/e8a8d645-3ac2-4673-a484-96c0dfb47bea@googlemail.com

 · 

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: dirk.krautschick@googlemail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: pg_repack vs. running logical/physical replication
  In-Reply-To: <e8a8d645-3ac2-4673-a484-96c0dfb47bea@googlemail.com>

* 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