From: | Axel Rau <Axel(dot)Rau(at)Chaos1(dot)DE> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | [RESOLVED] Re: Can't drop subscription |
Date: | 2022-02-23 20:47:02 |
Message-ID: | EBE2158F-70B7-4E09-99ED-1F1DFF7D7F4C@Chaos1.DE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> Am 21.02.2022 um 19:22 schrieb Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> Axel Rau <Axel(dot)Rau(at)Chaos1(dot)DE> writes:
>> This was the error message from an ansible script. I assumed, ansible did the quoting.
>> Doing it per hand, works:
>
> Seems likely that the ansible script is connecting to a different
> database. Log-rep subscriptions are database-local objects, not
> cluster-wide, so it matters.
The problem did not happen again after I did a clean clone, where I let CREATE SUBSCRIPTION create the slot.
I implemented this recipe [1] in ansible and it upgraded 2 subscribers and one publisher in 4 minutes from 12 to 13. (-;
Thanks for all your help,
Axel
[1] https://elephanttamer.net/?p=58 <https://elephanttamer.net/?p=58>
---
PGP-Key: CDE74120 ☀ computing @ chaos claudius
From | Date | Subject | |
---|---|---|---|
Next Message | Peter J. Holzer | 2022-02-24 07:49:55 | Re: pg_upgrade from Postgresql-12 to Postgresql-13 fails with "Creating dump of database schemas postgres *failure*" |
Previous Message | Axel Rau | 2022-02-23 20:46:43 | [RESOLVED] Re: restarting logical replication after upgrading standby |