From: | Rijo Roy <rjo_roy(at)yahoo(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Barman issue |
Date: | 2018-10-05 09:50:55 |
Message-ID: | 175753061.5116038.1538733055387@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello Experts,
I have a server rhel 6.9 installed with barman 2.3 which is configured to take backup from Postgresql 10 installed in a remote host and the same is working.
I am trying to do a poc on streaming backup and streaming wal method by making use of the pg_receivewal. I have already created a user with replication privilege the same is added in pg_hba. conf. And I am able to connect remotely using the user created.
But when I am running barman check pg
pg is the name given to the remote dB host. I am getting an error like this
EXCEPTION: LooseVersion instance has no attribute 'version'
Below I am pasting the conf files used:
[pg]
conninfo
streaming_conninfo
streaming_archiver = on
slot_name = barman
backup_method = postgres
path_prefix = Postgresql bin path
basebackups_directory
errors_directory
incoming_wals_directory
streaming_wals_directory
-------—-----------------------------------
I have already created the replication slots and started the pg_receivexlog remotely from the batman server. Was are streaming and is coming to the incoming_wals_directory
Please note that there are 2 more servers configured with barman in this backup hosts which is working fine.. The o my difference theyvhave is that they are configured with backup_method = rsync.
I wanted to make use of pg_receivexlog instead of rsync. Hence this poc..
Please help.
Thanks,
Roy
Sent from Yahoo Mail on Android
From | Date | Subject | |
---|---|---|---|
Next Message | deepikags | 2018-10-05 09:54:58 | Does postgreSQL community edition supports data distribution across nodes |
Previous Message | Laurenz Albe | 2018-10-05 06:38:55 | Re: We are facing "PANIC: could not read from control file:Success error while starting the database. |