Message-ID: <1507187247.3119.1.camel@cybertec.at>
Subject: Re: streaming replication corruption Q's
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: ghiureai <isabella.ghiurea@nrc-cnrc.gc.ca>, "pgsql-admin@postgresql.org"
	 <pgsql-admin@postgresql.org>
Date: Thu, 05 Oct 2017 09:07:27 +0200
In-Reply-To: <59D5300C.4030701@nrc-cnrc.gc.ca>
References: <59D5300C.4030701@nrc-cnrc.gc.ca>
Organization: Cybertec
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

ghiureai wrote:
> I'm reading PG 10 streaming replication manual, I would like to learn 
> from your expertise if this type of replication will  copy a bad  
> segment/bit corrupt from master to slave host , will this possible to 
> happened ?

Streaming replication happens on a physical level, so it does not pay
attention to logical consistency.
If the primary is suffering from data corruption, every data
modification containing that data corruption will be replicated.

>   What are the most common issues  you seeing when running streaming 
> replication,  any  files/bits corruption (  from my understanding 
> logical replication will replicate data corruption)where do you have to 
> pay attention when setting up a new system like this ,

That question is too general...

Make sure that you are running the same operating system version on
(ideally) the same hardware on all machines.

Either set wal_keep_segments high enough or (more cumbersome, but
more reliable) configure WAL shipping as a fallback when the
standby has a longer down time.

Yours,
Laurenz Albe


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin