Score:0

repmgr for streaming replication - standby register

gb flag

I'm testing repmgr tool and I'm a little bit confused. Everything's fine until standby register step.

What should I have configured on standby server? From docs I assumed that standby should't have the cluster, but it didn't configure a new one. When the postgres cluster exists repmgr have a problem with existing data. When I'll stop the cluster service and delete the data manually and run the migration from repmgr I have an error after starting the cluster:

postgres@ip-10-0-34-147:~$ /usr/lib/postgresql/13/bin/pg_ctl -D /var/lib/postgresql/13/main start
waiting for server to start....postgres: could not access the server configuration file "/var/lib/postgresql/13/main/postgresql.conf": No such file or directory
 stopped waiting
pg_ctl: could not start server
Examine the log output.

It's running on Ubuntu, but maybe more applicable will be Debian. But I still have no idea how to make it right.

Score:0
gb flag

It worked without any problems under Debian 10 Buster OS.

After:

  • stopping PostgreSQL service on the standby server,
  • removing PostgreSQL data from the standby server,
  • running data migration job from primary to standby server,

the PostreSQL service has started with migrated data as a standby server.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.