My client recovery.conf looks this way:
standby_mode = 'on'
primary_conninfo = 'host=arcserver1 port=5432 user=postgres pass=postgres'
restore_command = 'pg_standby /db/pg_archived %f %p >> /var/log/standby.log'
primary_slot_name='standby1'
Zitat von Andreas Kretschmer <andreas@a-kretschmer.de>:
> Do you have a client with a propper recovery.conf running?
>
> Am 19. Oktober 2015 09:58:40 MESZ, schrieb "Sven Löschner" <sven@someko.de>:
>> I have the following problem: i am trying to set up a streaming
>> replication scenario with load balancing. I read various tutorials but
>>
>> i cannot find the mistake. The replication does not work. I do not
>> have a "wal sender/receiver process". The archiving works and
>> everytime the master restarts, the archived wal files are copied to
>> the slave. I even do not get any error. And in configuration file(s)
>> everything looks like fine for me, e.g. master:
>>
>> wal_level = hot_standby
>> wal_keep_segments = 32
>> max_wal_senders = 5
>> max_replication_slots = 5
>> wal_sender_timeout = 60s
>>
>> What irritates me the most is that there is no "wal sender process"
>> and there is no error thrown.
>>
>> Thank you for any idea,
>> Sven
>>
>>
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
