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 1gNMFe-0006ry-L7 for pgsql-admin@arkaria.postgresql.org; Thu, 15 Nov 2018 18:20:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gNMDT-0001bK-Rs for pgsql-admin@arkaria.postgresql.org; Thu, 15 Nov 2018 18:18:11 +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 1gNMDT-0001au-G7 for pgsql-admin@lists.postgresql.org; Thu, 15 Nov 2018 18:18:11 +0000 Received: from 48.23.240.77.static.louhi.net ([77.240.23.48] helo=vcust561.louhi.net) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gNMDR-0007VR-Av for pgsql-admin@postgresql.org; Thu, 15 Nov 2018 18:18:10 +0000 Received: from localhost.localdomain (mobile-access-5d6a27-192.dhcp.inet.fi [93.106.39.192]) (authenticated bits=0) by vcust561.louhi.net (8.14.7/8.14.7/0) with ESMTP id wAFIHx74022670 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 15 Nov 2018 20:18:00 +0200 DKIM-Filter: OpenDKIM Filter v2.11.0 vcust561.louhi.net wAFIHx74022670 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kolttonen.fi; s=mail; t=1542305880; bh=v2qZCkBvnFPocMeQwYkMquIoThNrCOrqdzNfpWHHp8Y=; h=Date:From:To:Subject:From; b=anire8Q6ofdwmhpdOwwRE8SokvqwVT5M/UTmoRQbXnS8RSsc8Pi32sgkXf17vdNJu uOutO2zq1mHkT2pA9y5Pp3Bm2pYkN++q4rT/JPXvUXrz08sQi6QoXRBDiNL91DEI1W PMUAkptnrPSePwsjYc06Vr7wHML3/1LQIFjPa+283YUzwcYvChai8a8eccIsqq/uZd LV1+76rTGjiNK47lOBjHULRwYgzuy0tHIhsb7oc18cbsyU5nDGXeV9FhT3nCDpZB3v /6/kf2ks0OQ3SA0xZT4Ojzk0OTTn+lGWvycUDheBc3nnsKEDnnzJH6YXoWDENpms5S ijhHIhPQVTGCQ== Date: Thu, 15 Nov 2018 20:18:02 +0200 (EET) From: pgsql-admin@kolttonen.fi To: pgsql-admin@postgresql.org Subject: The current shape of PG master-slave replication Message-ID: User-Agent: Alpine 2.21 (LFD 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello! I am a happy PostgreSQL user, but I have never tried PG replication at all. Based on my vague recollections concerning the past, MySQL used to have the advantage of having a pretty stable and working master-slave replication when PG did not have such a thing. But PG has been more SQL-compliant, has had foreign keys forever, and in general, I guess PG has had a more advanced feature set available. I have followed the progress of PostgreSQL regarding replication just occasionally, but not very actively. Master-slave replication is now officially supported in the newest releases, maybe has been for a long time, I am not sure. In any case it is not my intention to spark a heated discussion about the merits of MySQL/MariaDB vs PostgreSQL. All I am asking is maybe hearing some observations of PG admins out there. To be concrete, if I use PG 10.x master-slave replication in production, is it very reliable when set up properly? Any practical experiences? Well, I suppose it *must* be reliable, but I am interested in hearing of possible problems, too. Thanks for the information. Best regards, Unto Sten