Re: BDR: ALTER statement hanging

From: Selim Tuvi <stuvi(at)ilm(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Sylvain MARECHAL <marechal(dot)sylvain2(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: BDR: ALTER statement hanging
Date: 2015-12-08 16:50:20
Message-ID: D702486C6BC79C40A9C6FF4F0315ABC0433AB9BD@mailbox12.lucas.alllucas.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks Craig, the problem was that (if I remember correctly) there were absolutely no errors or warnings logged when I issued the ALTER statement. Everything seemed to operate normally except that the execution never completed. Even the fact that the node_status was set to 'i' didn't result in any log messages and the replication was working as it should.

-Selim

________________________________
From: Craig Ringer [craig(at)2ndquadrant(dot)com]
Sent: Sunday, December 06, 2015 7:05 PM
To: Selim Tuvi
Cc: Sylvain MARECHAL; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] BDR: ALTER statement hanging

​If you're not sure what's going on on a node, look at its logs.

The background worker API and PostgreSQL's lack of autonomous transactions makes it quite challenging for BDR workers to capture logs and expose them to users at the SQL level. So always, if in doubt, examine the log files.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message anj patnaik 2015-12-08 17:00:31 error on pg_restore
Previous Message Chris Withers 2015-12-08 12:21:46 Re: union/difference/intersection question