On Thu, May 8, 2025 at 8:54 AM Luca Ferrari <fluca1...@gmail.com> wrote: > > I've pgbackrest making backups, so I have an archive_command. I'm > going to see if putting a restore_command can fix the problem. >
But I'm facing a quite trivial problem: in ubuntu installation the configuration files are separated from the PGDATA. Apparently pg_rewind is trying to read postgresql.conf to get the restore_command, and I don't know how to specify the different location of the postgresql.conf (cannot specifcy -c as in postgres): $ /usr/lib/postgresql/17/bin/pg_rewind -D /var/lib/postgresql/17/main --source-server="user=replica_fluca host=dev-psqlha3 dbname=replica_fluca" -R -P --debug -c postgres: could not access the server configuration file "/var/lib/postgresql/17/main/postgresql.conf": No such file or directory no data was returned by command "/usr/lib/postgresql/17/bin/postgres -D /var/lib/postgresql/17/main -C restore_command" child process exited with exit code 2 pg_rewind: error: could not read restore_command from target cluster Any idea? Clearly, postgresql.auto.conf is within PGDATA, and since my recovery_command is there, one trick could be to touch and empty PGDATA/postgresql.conf, pg_rewind, remove the fake configurtion file. But I'm sure there is a smarter solution. Thanks, Luca
