Quick Links

Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database

From:	Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To:	Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc:	vignesh C <vignesh21(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, "exclusion(at)gmail(dot)com" <exclusion(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject:	Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
Date:	2025-08-14 08:48:27
Message-ID:	CAA4eK1KQMVtKUe-pqzRKeoFLaOS08_S0jirKgzePvRGN_9B8Tg@mail.gmail.com
Views:	Whole Thread \| Raw Message \| Download mbox \| Resend email
Thread:
Lists:	pgsql-bugs

On Thu, Aug 14, 2025 at 2:05 PM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>
> Yeah this looks fine to me. PFA patches for back branches.
>

Can we add a test based on the scenario reported in this email?

--
With Regards,
Amit Kapila.

In response to

Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database at 2025-08-14 08:35:32 from Dilip Kumar

Responses

Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database at 2025-08-14 11:02:29 from Dilip Kumar

Browse pgsql-bugs by date

	From	Date	Subject
Next Message	Sergei Kornilov	2025-08-14 09:22:36	Re: BUG #19018: high memory usage and "stack depth limit exceeded", with GiST index on ltree
Previous Message	Dilip Kumar	2025-08-14 08:35:32	Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database