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 1tQ4z0-00HWkv-Hy for pgsql-general@arkaria.postgresql.org; Tue, 24 Dec 2024 13:29:59 +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 1tQ4yz-005NSx-Ac for pgsql-general@arkaria.postgresql.org; Tue, 24 Dec 2024 13:29:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tQ4yy-005NRh-Ts for pgsql-general@lists.postgresql.org; Tue, 24 Dec 2024 13:29:56 +0000 Received: from mail-ot1-x332.google.com ([2607:f8b0:4864:20::332]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tQ4yv-001ORw-Bt for pgsql-general@postgresql.org; Tue, 24 Dec 2024 13:29:56 +0000 Received: by mail-ot1-x332.google.com with SMTP id 46e09a7af769-71e36b27b53so2621776a34.1 for ; Tue, 24 Dec 2024 05:29:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1735046992; x=1735651792; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=NjKnLLKLR28CzyY86+4IkqLsdZpVWhlInfUIEC7XWPM=; b=dyfraNP8C4Vwq59Nin4y2FyMxgf05u+35CwcY51xDaE3n/n3qkyPTOTkw6wcPIO7Go wo3hEnH0SSJCPuNyPazb/vFn020k/IFv+BGLf8qJfXAZsT8Lvcbp7ATonCDFo6K9lwY3 E/Q0WV3lP8fmNS5YdQ+op/uuzjI+OUAgKYioBWMVFx/mdFK3ppySIc5g+05NrJ5GLmqM CDMQsKdYNn1s7yjfC2vfZb0oeAMJ4FXJVnA+M6NBKlF0N1QLOcii4DV0QLlThxqcebYv o7tPr+tI6jNEF4iJ1qhmgqU6nqStzJuWJ0VXaozG6jKMEh1z/RhQlcgRzGFjygYyeZiq SFIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1735046992; x=1735651792; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=NjKnLLKLR28CzyY86+4IkqLsdZpVWhlInfUIEC7XWPM=; b=mxU90FiBGtTi0oa0niVyapIr3uSZFwu7wxc9OiqoBiYHV/9FODQe2USOANNREGgOHt HLU9hRA8pvY7MT8tU+ZurERBiARR+3wS1W5GpckHmbiAepTF+ltFTUvM9tDvtuh2B1ao o7Uny+6+UPi5N6pO4xDQfvLGinz5PsOu1OyAfuHKVJFdxyxqsArebKU4IJJq0RWAge07 CAfqGhS2SWen6/gtchbOqV1Fqhfg4/V/j8OgD3V7nNDE6dWxC5RuPiabXlpujXJmMcgs Ub37lQeWGrxILM66H975y/Yqyah2dzd3xR/4y2BhCnkPHZxCi+ewGRD8Brycpw2XIoWl yrkA== X-Gm-Message-State: AOJu0YxCvqwAFf3cph1vTlZUDUWIxBB2vdouXcmFzw/40AFKYM+rdoIy YUSOS3UE8CSFpnKE4BmKlMib220c3Q0uFc3jYm382g3KfdXM1uMU/I5SvpMbLX8nPkVSuKAxrtg i0veOPQgqf2K5lVlap5W4NADTIcmxmoA/ X-Gm-Gg: ASbGncsxtg+1eKbJ4Qf09hx0pNw/nGYbbbiU6hgS8xqXJXwyhDxdNM39/2fB5hqqlhL 1TDfUlDMkTnCT+Z1xFJeDd3b498DE0AAb9fM5XbQ= X-Google-Smtp-Source: AGHT+IEN2ektV1Iaj/xICJulDB20/Okw6rDNNO5B5y4/8O8vHjNGgIhdHFQnDSswNj9YpUAyvxCUFRtfogF3qrBLHtY= X-Received: by 2002:a05:6870:7a10:b0:29e:9dc:8ba with SMTP id 586e51a60fabf-2a7fb30d5ddmr10608823fac.27.1735046991582; Tue, 24 Dec 2024 05:29:51 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Tue, 24 Dec 2024 08:29:40 -0500 Message-ID: Subject: Re: repmgr(d) versions 5.5 vs 5.4 from apt.postgresql.org To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000009a1d26062a041b21" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009a1d26062a041b21 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Dec 24, 2024 at 4:28=E2=80=AFAM Matthias Leisi = wrote: > 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_time= out=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; extensio= n > 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? > This [HINT] says that YOU are supposed to run the ALTER EXTENSION command: [quote] update the installed extension version by executing "ALTER EXTENSION repmgr UPDATE" [/quote] --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --0000000000009a1d26062a041b21 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Dec 24, 2024 at 4:28=E2=80=AFAM M= atthias Leisi <matthias@leisi.net<= /a>> wrote:
I installed Postgres 16/17= from apt.postgresq= l.org=C2=A0(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 =C2=A0--version
repm= gr 5.5.0
postgres@dev-pgcl01:~$ /usr/lib/postgresql/16/bin/repmgr= =C2=A0--version
repmgr 5.5.0

root@= dev-pgcl01:~# apt-cache show postgresql-17-repmgr | grep "Filename&quo= t;
Filename: pool/main/r/repmgr/postgresql-17-repmgr_5.5.0-2.pgdg= 120+1_arm64.deb

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

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

repmgr.conf is minimalistic:

node_id=3D= 1
node_name=3Dnode1
conninfo=3D'host=3D10.20.70.26 = user=3Drepmgr dbname=3Drepmgr connect_timeout=3D2'
data_direc= tory=3D'/var/lib/postgresql/17/'
failover=3Dautomatic
use_replication_slots=3Dtrue
promote_command=3D'/usr/b= in/repmgr standby promote -f /etc/postgresql/17/main/repmgr.conf --log-to-f= ile'
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

<= div>/usr/lib/postgresql/17/bin/repmgr -f /etc/postgresql/17/main/repmgr.con= f primary register

And it shows what I would expec= t:

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=3Dre= pmgr host=3D10.20.70.26 fallback_application_name=3Drepmgr options=3D-csear= ch_path=3D"
DEBUG: connecting to: "user=3Drepmgr connec= t_timeout=3D2 dbname=3Drepmgr host=3D10.20.70.26 fallback_application_name= =3Drepmgr options=3D-csearch_path=3D"
=C2=A0ID | Name =C2=A0= | Role =C2=A0 =C2=A0| Status =C2=A0 =C2=A0| Upstream | Location | Priority = | Timeline | Connection string
----+-------+---------+-----------= +----------+----------+----------+----------+------------------------------= ----------------------------------------------------------
=C2=A0= 1 =C2=A0| node1 | primary | * running | =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|= default =C2=A0| 100 =C2=A0 =C2=A0 =C2=A0| 1 =C2=A0 =C2=A0 =C2=A0 =C2=A0| h= ost=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/repm= grd -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] se= t_config():
=C2=A0 SET synchronous_commit TO 'local'
[2024-12-24 09:21:25] [DEBUG] expected extension version: 50500; exte= nsion version: 50400
[2024-12-24 09:21:25] [ERROR] this "rep= mgr" 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 vers= ion 5.4
[2024-12-24 09:21:25] [HINT] update the installed extensi= on version by executing "ALTER EXTENSION repmgr UPDATE" in the re= pmgr database


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

shows version 5.4

The sugg= ested 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?

This = [HINT] says that YOU are supposed=C2=A0to run the ALTER EXTENSION command:<= /div>
[quote]
update the installed extension version by execu= ting "ALTER EXTENSION repmgr UPDATE"
[/quote]

--
Death to <Redacted>,= and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
--0000000000009a1d26062a041b21--