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:
Hola,
hay una portal en espanol sobre postgres con listas de correo y IRC:
http://www.postgresql-es.org/comunidad
Aqui hablamos ingles. Sorry.
saludos desde Alemana.
Matthias
Am Dienstag, 4. Januar 2011, um 21:26:33 schrieb liliana lazarte:
Hola gente:
Estoy haciendo un funcion que
Hi Ben,
load balancing is not possible with the tools that are in the postgres
installation. There is no automatic switch-over to a slave if the master
fails. The trigger file needs to be created to make a slave to the master. This
is not done automaitcally by postgres, but should be done by a
I don't know slony that much. I used WAL processing. But since 9.0 I prefer
Hot-Streaming replication. This link is a good starting point - besides the
documentation.
http://it.toolbox.com/blogs/database-soup/5-minutes-to-binary-
replication-41873
A solution for your problem might be a second