Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEw9p-00AU1h-MK for pgsql-general@arkaria.postgresql.org; Sat, 23 Nov 2024 19:51:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tEw9m-003WOM-0W for pgsql-general@arkaria.postgresql.org; Sat, 23 Nov 2024 19:51:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEw9l-003WOC-C4 for pgsql-general@lists.postgresql.org; Sat, 23 Nov 2024 19:51:01 +0000 Received: from mail.thenautilus.net ([178.162.154.203]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEw9e-003Q2E-EN for pgsql-general@lists.postgresql.org; Sat, 23 Nov 2024 19:51:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=thenautilus.net; h=date :from:to:subject:message-id:mime-version:content-type :content-transfer-encoding; s=20240114; bh=BI3PIOIyDyhKGYq0CjVYR LZpg3KSLl7uPR8Senb6k5g=; b=ZWgJdmv2NobhQv6APVVpK1lVsvf2GGr9OFHeG p3CI/SaCOCo0DOyhxXH2uHYmxgVWtL17BodOWS+br3GmIrHkY8NCdvkl4ijPpqsG W6IULynVpSHnF8l3IpBhClOzsipBJrpVT17/RUDTWm1neg7bO8rjNqSxjdMDBNQa mlGWlEHMNVS945Kg9uniWCaZEC0w23vAKyOgk0K+oWhsJl31bb1S0QdFVZRBXPo+ Y/TsolmQtswTaU0RIpOZK/4Vp5S6U5oR88M644KdnCxM34qEkga/pLkDJGEYOk+B NPycojVkkKjTCQf/dZdBsynIeyfjHXCuh7X5W6cqMoLAJWUbA== Received: (qmail 30541 invoked from network); 23 Nov 2024 19:50:50 -0000 Received: from unknown (HELO localhost) (dakkar@::ffff:81.187.173.38) by 0 with ESMTPA; 23 Nov 2024 19:50:50 -0000 Date: Sat, 23 Nov 2024 19:50:50 +0000 From: Gianni Ceccarelli To: pgsql-general@lists.postgresql.org Subject: Version upgrades and replication Message-ID: <20241123195050.2098ba7e@thenautilus.net> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.41; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello all! I have a primary+replica PostgreSQL that I think work fine. I created the replica's data directory using:: pg_basebackup -D $datadir -h $primary_host -U $replicauser \ --write-recovery-conf \ --create-slot --slot=3D$slotname=20 after creating the user on the primary (``CREATE ROLE replicauser WITH REPLICATION PASSWORD 'password' LOGIN``) and allowing connections in ``pg_hba.conf`` Everything looks fine, changes on the primary can be seen on the replica. First question: what's the name of this replication mode? Every time I try to read the documentation I get confused about which is which=E2=80=A6 I initially created the replica on PostgreSQL 16. Yesterday I upgraded to 17: stop the 16 primary, stop the 16 replica, ``pg_upgrade17`` on the primary, start the 17 primary, re-do the whole base backup with ``pg_basebackup17`` on the replica, start the 17 replica, everything works like before. Second question: is there a better way to do that? Without having to copy the whole cluster data again from scratch? Thanks in advance! --=20 Dakkar - GPG public key fingerprint =3D A071 E618 DD2C 5901 9574 6FE2 40EA 9883 7519 3F88 key id =3D 0x75193F88