Thread: Can't drop subscription
While following this receipt: https://elephanttamer.net/?p=58 I’ getting: ERROR: subscription \"meteo\" does not exist“ with this command: psql -c \"DROP SUBSCRIPTION meteo\“ Same on both subscribers: - - - operations=# select oid,subdbid,subname,subowner,subenabled,subslotname,subpublications from pg_catalog.pg_subscription; oid | subdbid | subname | subowner | subenabled | subslotname | subpublications -------+---------+---------+----------+------------+-------------+----------------- 16451 | 16388 | meteo | 10 | t | meteo_dbb4 | {meteo} (1 row) - - - operations=# select oid,subdbid,subname,subowner,subenabled,subslotname,subpublications from pg_catalog.pg_subscription; oid | subdbid | subname | subowner | subenabled | subslotname | subpublications -------+---------+---------+----------+------------+-------------+----------------- 16455 | 16388 | meteo | 16384 | t | meteo_dbb5 | {meteo} (1 row) - - - How can I drop the subscriptions? Shouldn’t there be 2 different subscriptions for 2 subscribers to the same publisher? Any help appreciated, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius
On 2/21/22 11:28 AM, Axel Rau wrote: > While following this receipt: > https://elephanttamer.net/?p=58 > I’ getting: > ERROR: subscription \"meteo\" does not exist“ > with this command: > psql -c \"DROP SUBSCRIPTION meteo\“ Why the backslashes, instead of: psql -c "DROP SUBSCRIPTION meteo;“ (Presumably you're defining the host and database in PG* environment variables?) > Same on both subscribers: > - - - > operations=# select oid,subdbid,subname,subowner,subenabled,subslotname,subpublications from pg_catalog.pg_subscription; > oid | subdbid | subname | subowner | subenabled | subslotname | subpublications > -------+---------+---------+----------+------------+-------------+----------------- > 16451 | 16388 | meteo | 10 | t | meteo_dbb4 | {meteo} > (1 row) > - - - > operations=# select oid,subdbid,subname,subowner,subenabled,subslotname,subpublications from pg_catalog.pg_subscription; > oid | subdbid | subname | subowner | subenabled | subslotname | subpublications > -------+---------+---------+----------+------------+-------------+----------------- > 16455 | 16388 | meteo | 16384 | t | meteo_dbb5 | {meteo} > (1 row) > - - - > > How can I drop the subscriptions? > > Shouldn’t there be 2 different subscriptions for 2 subscribers to the same publisher? > > Any help appreciated, > Axel > --- > PGP-Key: CDE74120 ☀ computing @ chaos claudius > > > -- Angular momentum makes the world go 'round.
Am 21.02.2022 um 18:34 schrieb Ron <ronljohnsonjr@gmail.com>:
Why the backslashes, instead of:
psql -c "DROP SUBSCRIPTION meteo;“
Doing it per hand, works:
- - -
Why the backslashes, instead of:
psql -c "DROP SUBSCRIPTION meteo;“
- - -
I will put the command into a file and give that per -f to psql.
Thanks for answering, Axel
---
PGP-Key: CDE74120 ☀ computing @ chaos claudius
PGP-Key: CDE74120 ☀ computing @ chaos claudius
Axel Rau <Axel.Rau@Chaos1.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. regards, tom lane
Am 21.02.2022 um 19:22 schrieb Tom Lane <tgl@sss.pgh.pa.us>:Axel Rau <Axel.Rau@Chaos1.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.
I implemented this recipe [1] in ansible and it upgraded 2 subscribers and one publisher in 4 minutes from 12 to 13. (-;
Axel