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

help / color / mirror / Atom feed
From: Michael Banck <michael.banck@credativ.de>
To: Magnus Hagander <magnus@hagander.net>
Cc: Sergei Kornilov <sk@zsrv.org>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Offline enabling/disabling of data checksums
Date: Thu, 14 Mar 2019 14:59:28 +0100
Message-ID: <1552571968.9697.2.camel@credativ.de> (raw)
In-Reply-To: <CABUevEw5X1jH5P3goyEdk1Tyby7QpyJ6q4c-D-sjEPHoZ1gw_A@mail.gmail.com>
References: <20181221201616.GD4974@nighthawk.caipicrew.dd-dns.de>
	<20190311045323.GE1818@paquier.xyz>
	<155231347133.16480.11453587097036807558.pgcf@coridan.postgresql.org>
	<1552385626.4947.50.camel@credativ.de>
	<20190312124403.GM13812@paquier.xyz>
	<20190313021621.GP13812@paquier.xyz>
	<alpine.DEB.2.21.1903130805330.4059@lancre>
	<20190313093150.GE2988@paquier.xyz>
	<alpine.DEB.2.21.1903131037240.4059@lancre>
	<20190313101021.GF2988@paquier.xyz>
	<5217311552474471@myt2-66bcb87429e6.qloud-c.yandex.net>
	<CABUevEzM86WSaap-OZ0Dfou8T07NN1ki5B67xd0u8UeZEpqT5Q@mail.gmail.com>
	<140161552477211@iva5-84bc572481fe.qloud-c.yandex.net>
	<CABUevExnUEaCafeswWU_MK4WmY10EDQ-kjPTj3i_Eb=AOJgOOA@mail.gmail.com>
	<1552492283.4947.73.camel@credativ.de>
	<CABUevEw5X1jH5P3goyEdk1Tyby7QpyJ6q4c-D-sjEPHoZ1gw_A@mail.gmail.com>

Hi,

Am Mittwoch, den 13.03.2019, 17:54 +0100 schrieb Magnus Hagander:
> On Wed, Mar 13, 2019 at 4:51 PM Michael Banck <michael.banck@credativ.de> wrote:
> > Am Mittwoch, den 13.03.2019, 12:43 +0100 schrieb Magnus Hagander:
> > > I think this is dangerous enough that it needs to be enforced and not
> > > documented.
> > 
> > Changing the cluster ID might have some other side-effects, I think
> > there are several cloud-native 3rd party solutions that use the cluster
> > ID as some kind of unique identifier for an instance. It might not be an
> > issue in practise, but then again, it might break other stuff down the
> > road.
> 
> Well, whatever we do they have to update, right? 

Yeah, but I am saying their orchestrators might get confused about where
the old instance went and what this new thing with a totally different
systemid is and lose the connection between the two. 

Maybe that is a feature and not a bug.


Michael

-- 
Michael Banck
Projektleiter / Senior Berater
Tel.: +49 2166 9901-171
Fax:  +49 2166 9901-100
Email: michael.banck@credativ.de

credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer

Unser Umgang mit personenbezogenen Daten unterliegt
folgenden Bestimmungen: https://www.credativ.de/datenschutz




view thread (149+ messages)  latest in thread

Message-ID: <1552571968.9697.2.camel@credativ.de>
Permalink:  ../1552571968.9697.2.camel@credativ.de/
Also on:    postgresql.org/message-id/1552571968.9697.2.camel@credativ.de

 · 

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-hackers@postgresql.org
  Cc: michael.banck@credativ.de, magnus@hagander.net, sk@zsrv.org, michael@paquier.xyz, coelho@cri.ensmp.fr, pgsql-hackers@lists.postgresql.org
  Subject: Re: Offline enabling/disabling of data checksums
  In-Reply-To: <1552571968.9697.2.camel@credativ.de>

* 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