Thank you, Tatsuo and Tomasz, I appreciate your input, and the caveat
about the status. Just to satisfy my curiosity, would running
pcp_attach_node after startup be another acceptable solution to the
status problem?
Thank you,
AW
On Wed, Jun 15, 2011 at 7:24 PM, Tatsuo Ishii wrote:
What sho
On 16.06.2011 17:29, A W wrote:
Thank you, Tatsuo and Tomasz, I appreciate your input, and the caveat
about the status. Just to satisfy my curiosity, would running
pcp_attach_node after startup be another acceptable solution to the
status problem?
I don't think so.
I.e. imagine an application
Ah, of course. Thanks again.
On Thu, Jun 16, 2011 at 11:33 AM, Tomasz Chmielewski wrote:
> On 16.06.2011 17:29, A W wrote:
>>
>> Thank you, Tatsuo and Tomasz, I appreciate your input, and the caveat
>> about the status. Just to satisfy my curiosity, would running
>> pcp_attach_node after startup
I'm using pgpool-II + PostgreSQL 8.4 on three servers: primary + standby1 +
standby2. Replication mode is "on" Load balance mode is "on" (between
primary and standby1)
I followed the official tutorial to configure online recovery with PITR:
http://pgpool.projects.postgresql.org/pgpool-II/doc/pgpoo
Hi everyone. I'm using pgpool-II with PostgreSQL 9.0 in streaming replication
mode, and I'm able to get failover working correctly -- when the primary
(master) goes down, the slave is promoted and everything is great. However,
when I bring the primary back online using pcp_recovery_node, I fin
