Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ggnHE-0004YJ-F1 for pgsql-admin@arkaria.postgresql.org; Tue, 08 Jan 2019 09:02:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ggnHC-0004Fr-Vw for pgsql-admin@arkaria.postgresql.org; Tue, 08 Jan 2019 09:02:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ggnHC-0004Fj-MR for pgsql-admin@lists.postgresql.org; Tue, 08 Jan 2019 09:02:22 +0000 Received: from r0.smtpout1.paris1.alwaysdata.com ([2a00:b6e0:1:40:1:0:10:1]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ggnH8-00009n-KW for pgsql-admin@lists.postgresql.org; Tue, 08 Jan 2019 09:02:22 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alwaysdata.net; s=hexack; h=In-Reply-To:Content-Transfer-Encoding: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=VEV1KpvJofRI8CA+GzUM3rbDLWZowKizHZHbMUuDnnw=; b=nKVcihaHycMiV7GvrdE7u0MGxd iMZcB0JDBqSUNwgXtq0WpRGeQv90J2zgjXjFihk3XaFSOMwB1ZgUbGWt2hPotvxQICb0qE6XD3AFd EVdi7WfbEDtSWWN0fJsqv4aIz1sDP8g4ct4M6KTqH8NeEl7nCMlos4gWlhavDaYG228k=; Received: from mas01-1-78-225-200-186.fbx.proxad.net ([78.225.200.186] helo=office.hexack.fr) by smtpout1.paris1.alwaysdata.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ggnGb-0001ne-IU; Tue, 08 Jan 2019 10:01:45 +0100 Date: Tue, 8 Jan 2019 10:01:44 +0100 From: =?utf-8?B?U3TDqXBoYW5l?= KANSCHINE To: Natalie Wenz Cc: pgsql-admin@lists.postgresql.org Subject: Re: Database migration across different operating systems Message-ID: <20190108090144.rdrtfh6wznoolsww@office.hexack.fr> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: HexACK User-Agent: NeoMutt/20180716 X-alwaysdata-ID: 386696332 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hey ! Le lun. 7 janv., vers 22:51, Natalie Wenz exprimait : > > We are in an unusual circumstance, where we need to move all of our > Postgres 10 databases from their homes on servers running FreeBSD 11 > with ZFS to servers in another data center running Red Hat Linux 7.6 > (also with ZFS), with minimal downtime. > > I understand that the recommended, safest, approach would be to > dump/restore. We intend to do that wherever possible. It's not anymore since PostgreSQL have logical replication. You can initialize you FreeBSD cluster with a pg_basebackup and you follow updates with logical streaming. > However, we have some databases that require high > availability/minimal downtime that are also very large. (50 TB, for > example) With logical replication, is it's permanently up to date in miliseconds, you can switch when you want. > If it helps: The cpu architecture is the same on both hosts, and > we’ll be running Postgres with the same version and same build > options. Your OS or cpu architecture doesn't matter, really :-) Regards, -- Stéphane KANSCHINE - https://www.hexack.fr./ - https://www.nuajik.io./ @ stephane@hexack.fr  +33 6 64 31 72 52