| From: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
|---|---|
| To: | Willy-Bas Loos <willybas(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: londiste3: removing a node that does not exist |
| Date: | 2017-06-22 16:03:19 |
| Message-ID: | CAGnEbojLOBguO0Dmj69LGmKZfaEp+jNZ+ToDsSgPMQah-1Wq-A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2017-06-22 18:21 GMT+03:00 Willy-Bas Loos <willybas(at)gmail(dot)com>:
> Does anyone know of a method to get rid of the bad node and the data that
> it is gathering?
I also do not know the correct way to achieve this.
But once I needed to rename one of the queues to follow the internal naming
standard.
And I used the following queries on the provider node to prune _old_ queue:
SET search_path TO pgq_node;
DELETE FROM local_state WHERE queue_name='q-2rm';
DELETE FROM subscriber_info WHERE queue_name='q-2rm';
DELETE FROM node_info WHERE queue_name='q-2rm';
DELETE FROM node_location WHERE queue_name='q-2rm';
And restarted worker after that.
--
Victor Yegorov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Арсен Арутюнян | 2017-06-22 16:12:42 | SPI_execute_plan and vardata |
| Previous Message | Peter Eisentraut | 2017-06-22 15:43:34 | Re: pglogical vs. built-in logical replication in pg-10 |