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 1tQ1Dj-00H54L-Lg for pgsql-general@arkaria.postgresql.org; Tue, 24 Dec 2024 09:28:58 +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 1tQ1Di-003hgb-3R for pgsql-general@arkaria.postgresql.org; Tue, 24 Dec 2024 09:28:53 +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 1tQ1Dh-003hfw-AE for pgsql-general@lists.postgresql.org; Tue, 24 Dec 2024 09:28:53 +0000 Received: from mail-wm1-x32c.google.com ([2a00:1450:4864:20::32c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tQ1De-000K3f-1e for pgsql-general@postgresql.org; Tue, 24 Dec 2024 09:28:51 +0000 Received: by mail-wm1-x32c.google.com with SMTP id 5b1f17b1804b1-43625c4a50dso33736475e9.0 for ; Tue, 24 Dec 2024 01:28:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leisi.net; s=google; t=1735032528; x=1735637328; darn=postgresql.org; h=to:date:message-id:subject:mime-version:from:from:to:cc:subject :date:message-id:reply-to; bh=Z4u8G/tLK7nXEtr9hllyt+rtI08GtoX7CMzDCK4QkS0=; b=B4QjFIV7JML89wL3yZ8DAOq8kpuEi5ihKbGZWLSSn+848FRidq1fIKxKXKPIC7T7MP KwW8Fk3KuD1dwAjN/pDIGIIEhJ8ydZcZTIMZx0wDk+GnUzcojL+QB+iBysdsSDoNqtFK Xl0Uwm/p38eW31nz8A87TM3OfSfd08uGAmv2k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1735032528; x=1735637328; h=to:date:message-id:subject:mime-version:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Z4u8G/tLK7nXEtr9hllyt+rtI08GtoX7CMzDCK4QkS0=; b=K5ktLKA6hTAs6PqB+5thCiCHUViYo01RuodeSMmBZRmkAekDa9KuFkJ2fD1Ekz/DwN /iGYyolUvTb3oaBjUN9XiILQtSEfhmRW7HGR0uDKnlKJTUO4ikjbvzW2ftUnzgS1S3NG nkK1Np0fqYy/Ya+IAPRwHVC8+V7Z0ABcdOz/VeLi9tkXpJ+dgMJC82vsfOFpkY0IXXXO KrsxMnOHNIh1Oul6MoWdYf/P2zJairKNm+n6meJXKCZH6FsWWMU24XXUAEN66Ar48Xmi eiPdFNZDboTUa+QtPR8a5I9Z/50EaFkMzlihxKMa0evbNT92d9L5Ckt/2ffJcAgqZG3u 32MA== X-Gm-Message-State: AOJu0YxSK6hQSOB8AjqRsI9kMZzR5f9eBvt8VJVx1HMC42iMmGruM++v D9/hjgcilnRK1mbv8spcMGYGHjfgAXs/bwVFPRQBzY+rXxgUF6yf0n+zkSpDgHf0AwA8bpfYodk = X-Gm-Gg: ASbGnct9iH+o29aapYT2DXdFxLYb2dPkJFy0dJ10WZ8ONW14elHf/CNqcYAAMFR6i34 YF/mvCQ+R5fB0UBNgGB/7wmH3vpWJ7GyuwdeQqeN8QhVaPkmJvOxFP3owxcluzbSCDH4cE8DgJ/ JRQ00s9pd1zn54r+N71sFRnv72iv1sJtmXtmwO0zpDskK6HSs+efoCN2L4rRJ9B84PrcIMFUHEk 5kRYc4rys3D43O7R9YfqvYI1ct3n+L2aHuC2fp4xK4VI1Mm2A0veVP43eC9oyVzGvoQqqVi0nR9 1A== X-Google-Smtp-Source: AGHT+IFmwQMoQRg4Gpc7Mgjh5joCzXgcF5xws0i1l2YfetHuQf+U0fOrg8yhB91mlZnYFSgJDJlHIw== X-Received: by 2002:a05:600c:4510:b0:434:a29d:6c71 with SMTP id 5b1f17b1804b1-43668b782d2mr131215765e9.27.1735032527653; Tue, 24 Dec 2024 01:28:47 -0800 (PST) Received: from smtpclient.apple ([2a02:169:ce0e:0:e070:b5e9:fd29:ceb9]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-43656b3b207sm194508205e9.32.2024.12.24.01.28.47 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Dec 2024 01:28:47 -0800 (PST) From: Matthias Leisi Content-Type: multipart/alternative; boundary="Apple-Mail=_A5F6BEAD-C6D2-4E6E-987D-1C695B665BE2" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\)) Subject: repmgr(d) versions 5.5 vs 5.4 from apt.postgresql.org Message-Id: Date: Tue, 24 Dec 2024 10:28:36 +0100 To: pgsql-general X-Mailer: Apple Mail (2.3826.200.121) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail=_A5F6BEAD-C6D2-4E6E-987D-1C695B665BE2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I installed Postgres 16/17 from apt.postgresql.org = (with the intent of using version 17) on = Debian 12/Bookworm. Both have the same version of repmgr: postgres@dev-pgcl01:~$ /usr/lib/postgresql/17/bin/repmgr --version repmgr 5.5.0 postgres@dev-pgcl01:~$ /usr/lib/postgresql/16/bin/repmgr --version repmgr 5.5.0 root@dev-pgcl01:~# apt-cache show postgresql-17-repmgr | grep "Filename" Filename: = pool/main/r/repmgr/postgresql-17-repmgr_5.5.0-2.pgdg120+1_arm64.deb In postgresql.conf, I explicitly load the version 17 .so (just to be = sure it=E2=80=99s not loading something potentially different): shared_preload_libraries =3D '/usr/lib/postgresql/17/lib/repmgr.so' repmgr.conf is minimalistic: node_id=3D1 node_name=3Dnode1 conninfo=3D'host=3D10.20.70.26 user=3Drepmgr dbname=3Drepmgr = connect_timeout=3D2' data_directory=3D'/var/lib/postgresql/17/' failover=3Dautomatic use_replication_slots=3Dtrue promote_command=3D'/usr/bin/repmgr standby promote -f = /etc/postgresql/17/main/repmgr.conf --log-to-file' follow_command=3D'/usr/bin/repmgr standby follow -f = /etc/postgresql/17/main/repmgr.conf --log-to-file = --upstream-node-id=3D%n=E2=80=98 (plus a few configs about the logs) I created the cluster with /usr/lib/postgresql/17/bin/repmgr -f /etc/postgresql/17/main/repmgr.conf = primary register And it shows what I would expect: postgres@dev-pgcl01:~$ /usr/lib/postgresql/17/bin/repmgr -f = /etc/postgresql/17/main/repmgr.conf cluster show DEBUG: connecting to: "user=3Drepmgr connect_timeout=3D2 dbname=3Drepmgr = host=3D10.20.70.26 fallback_application_name=3Drepmgr = options=3D-csearch_path=3D" DEBUG: connecting to: "user=3Drepmgr connect_timeout=3D2 dbname=3Drepmgr = host=3D10.20.70.26 fallback_application_name=3Drepmgr = options=3D-csearch_path=3D" ID | Name | Role | Status | Upstream | Location | Priority | = Timeline | Connection string = ----+-------+---------+-----------+----------+----------+----------+------= ----+---------------------------------------------------------------------= ------------------- 1 | node1 | primary | * running | | default | 100 | 1 = | host=3D10.20.70.26 user=3Drepmgr dbname=3Drepmgr = connect_timeout=3D2 I attempt to start repmgrd with postgres@dev-pgcl01:~$ /usr/lib/postgresql/17/bin/repmgrd -v -f = /etc/postgresql/17/main/repmgr.conf --verbose Which gives the following log output: [2024-12-24 09:21:25] [NOTICE] repmgrd (repmgrd 5.5.0) starting up [2024-12-24 09:21:25] [INFO] connecting to database "host=3D10.20.70.26 = user=3Drepmgr dbname=3Drepmgr connect_timeout=3D2" [2024-12-24 09:21:25] [DEBUG] connecting to: "user=3Drepmgr = connect_timeout=3D2 dbname=3Drepmgr host=3D10.20.70.26 = fallback_application_name=3Drepmgr options=3D-csearch_path=3D" [2024-12-24 09:21:25] [DEBUG] set_config(): SET synchronous_commit TO 'local' [2024-12-24 09:21:25] [DEBUG] expected extension version: 50500; = extension version: 50400 [2024-12-24 09:21:25] [ERROR] this "repmgr" version is newer than the = installed "repmgr" extension version [2024-12-24 09:21:25] [DETAIL] "repmgr" version 5.5.0 providing = extension version 5.5.0 is installed but extension is version 5.4 [2024-12-24 09:21:25] [HINT] update the installed extension version by = executing "ALTER EXTENSION repmgr UPDATE" in the repmgr database SELECT * FROM pg_catalog.pg_extension WHERE extname =3D 'repmgr' shows version 5.4 The suggested ALTER EXTENSION from the log hint does not do anything I = could see. The same effect if I try the same using version 16. How to continue from here? What am I missing? Thanks for your help, =E2=80=94 Matthias --=20 Matthias Leisi Katzenr=C3=BCtistrasse 68, 8153 R=C3=BCmlang Mobile +41 79 377 04 43 matthias@leisi.net --Apple-Mail=_A5F6BEAD-C6D2-4E6E-987D-1C695B665BE2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I installed = Postgres 16/17 from apt.postgresql.org (with the = intent of using version 17) on Debian 12/Bookworm. Both have the same = version of repmgr:

postgres@dev-pgcl01:~$ = /usr/lib/postgresql/17/bin/repmgr  --version
repmgr = 5.5.0
postgres@dev-pgcl01:~$ /usr/lib/postgresql/16/bin/repmgr =  --version
repmgr = 5.5.0

root@dev-pgcl01:~# apt-cache show = postgresql-17-repmgr | grep "Filename"
Filename: = pool/main/r/repmgr/postgresql-17-repmgr_5.5.0-2.pgdg120+1_arm64.deb
<= /div>

In postgresql.conf, I explicitly load the = version 17 .so (just to be sure it=E2=80=99s not loading something = potentially = different):

shared_preload_libraries =3D = '/usr/lib/postgresql/17/lib/repmgr.so'

repmgr.con= f is = minimalistic:

node_id=3D1
node_nam= e=3Dnode1
conninfo=3D'host=3D10.20.70.26 user=3Drepmgr = dbname=3Drepmgr = connect_timeout=3D2'
data_directory=3D'/var/lib/postgresql/17/'<= /div>
failover=3Dautomatic
use_replication_slots=3Dtrue
promote_command=3D'/usr/bin/repmgr standby promote -f = /etc/postgresql/17/main/repmgr.conf = --log-to-file'
follow_command=3D'/usr/bin/repmgr standby = follow -f /etc/postgresql/17/main/repmgr.conf --log-to-file = --upstream-node-id=3D%n=E2=80=98

(plus a = few configs about the logs)

I created the = cluster with

/usr/lib/postgresql/17/bin/repmgr = -f /etc/postgresql/17/main/repmgr.conf primary = register

And it shows what I would = expect:

postgres@dev-pgcl01:~$ = /usr/lib/postgresql/17/bin/repmgr -f /etc/postgresql/17/main/repmgr.conf = cluster show
DEBUG: connecting to: "user=3Drepmgr = connect_timeout=3D2 dbname=3Drepmgr host=3D10.20.70.26 = fallback_application_name=3Drepmgr = options=3D-csearch_path=3D"
DEBUG: connecting to: "user=3Drepmgr= connect_timeout=3D2 dbname=3Drepmgr host=3D10.20.70.26 = fallback_application_name=3Drepmgr = options=3D-csearch_path=3D"
 ID | Name  | Role =    | Status    | Upstream | Location | Priority | = Timeline | Connection = string
----+-------+---------+-----------+----------+----------+= ----------+----------+----------------------------------------------------= ------------------------------------
 1  | node1 | = primary | * running |          | default =  | 100      | 1        | = host=3D10.20.70.26 user=3Drepmgr dbname=3Drepmgr = connect_timeout=3D2


I = attempt to start repmgrd = with

postgres@dev-pgcl01:~$ = /usr/lib/postgresql/17/bin/repmgrd -v -f = /etc/postgresql/17/main/repmgr.conf = --verbose

Which gives the following log = output:

[2024-12-24 09:21:25] [NOTICE] = repmgrd (repmgrd 5.5.0) starting up
[2024-12-24 09:21:25] = [INFO] connecting to database "host=3D10.20.70.26 user=3Drepmgr = dbname=3Drepmgr connect_timeout=3D2"
[2024-12-24 09:21:25] = [DEBUG] connecting to: "user=3Drepmgr connect_timeout=3D2 dbname=3Drepmgr = host=3D10.20.70.26 fallback_application_name=3Drepmgr = options=3D-csearch_path=3D"
[2024-12-24 09:21:25] [DEBUG] = set_config():
  SET synchronous_commit TO = 'local'
[2024-12-24 09:21:25] [DEBUG] expected extension = version: 50500; extension version: 50400
[2024-12-24 09:21:25] = [ERROR] this "repmgr" version is newer than the installed "repmgr" = extension version
[2024-12-24 09:21:25] [DETAIL] "repmgr" = version 5.5.0 providing extension version 5.5.0 is installed but = extension is version 5.4
[2024-12-24 09:21:25] [HINT] update = the installed extension version by executing "ALTER EXTENSION repmgr = UPDATE" in the repmgr = database


SELECT = * FROM pg_catalog.pg_extension WHERE extname =3D = 'repmgr'

shows version = 5.4

The suggested ALTER EXTENSION from the log = hint does not do anything I could see.

The same = effect if I try the same using version 16.

How = to continue from here? What am I = missing?

Thanks for your help,
=E2=80=94= Matthias

-- 
Matthias = Leisi
Katzenr=C3=BCtistrasse 68, 8153 R=C3=BCmlang
Mobile +41 79 = 377 04 43
matthias@leisi.net



= --Apple-Mail=_A5F6BEAD-C6D2-4E6E-987D-1C695B665BE2--