From: Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
To: vignesh C <vignesh21@gmail.com>
Cc: exclusion@gmail.com <exclusion@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: RE: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
Date: Thu, 31 Jul 2025 09:03:58 +0000
Message-ID: <OSCPR01MB14966AAD2EEA95C752DB8904CF527A@OSCPR01MB14966.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAFiTN-s=iHQ+4u=6qOeNvGrrJ4J7ysfJbejsDx7D4Kpdo1xttA@mail.gmail.com>
References: <18988-7312c868be2d467f@postgresql.org>
<CALDaNm0wf0XVKmcf=s2e3d52b4VS9wkBao1HC9rXJB=n5Mxs2g@mail.gmail.com>
<CAFiTN-s=iHQ+4u=6qOeNvGrrJ4J7ysfJbejsDx7D4Kpdo1xttA@mail.gmail.com>
Dear Vignesh, Dilip,
I found another corner case:
```
postgres=# CREATE SUBSCRIPTION sub CONNECTION 'dbname=db1 user=postgres port=5431' PUBLICATION pub1 WITH (connect=false, slot_name=sub);
WARNING: subscription was created, but is not connected
HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription.
CREATE SUBSCRIPTION
postgres=# DROP SUBSCRIPTION sub ;
... (won't return)
```
Because still can explicitly specify the slot_name while creating the subscription.
Another pattern is to run ALTER SUBSCRIPTION SET (slot_name) command after the
CREATE SUBSCRIPTION WITH (connect=false);.
Should we fix the case? If so, how?
Best regards,
Hayato Kuroda
FUJITSU LIMITED
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: kuroda.hayato@fujitsu.com, dilipbalaut@gmail.com, vignesh21@gmail.com, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: RE: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
In-Reply-To: <OSCPR01MB14966AAD2EEA95C752DB8904CF527A@OSCPR01MB14966.jpnprd01.prod.outlook.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox