WAL sender process starts when streaming client is active. The connection
is initiated by the client. That's why you cannot see it. It also uses the
TCP-port that is used by any other pg client. There is a special entry in
the pg_hba.conf for the replication clients. Refer to this please:
http://ww
On 2015-10-19 08:34:51 +, Sven Löschner wrote:
> 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='stan
On 19 October 2015 at 09:41, Sven Löschner wrote:
> I inserted the following in my pg_hba.conf to test, but it does not work:
>
> hostreplication rep_user0.0.0.0/0 trust
> hostall postgres0.0.0.0/0 trust
>
> thank you in advan
I inserted the following in my pg_hba.conf to test, but it does not work:
hostreplication rep_user0.0.0.0/0 trust
hostall postgres0.0.0.0/0 trust
thank you in advance,
Sven
WAL sender process starts when streaming client i
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 :
Do you have a client
Do you have a client with a propper recovery.conf running?
Am 19. Oktober 2015 09:58:40 MESZ, schrieb "Sven Löschner" :
>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 repl
