Re: CountDBSubscriptions check in dropdb

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
Subject: Re: CountDBSubscriptions check in dropdb
Date: 2019-11-09 12:07:27
Message-ID: CAA4eK1L+1irgi+8QtFbj4jpiZ69KVEvK+spDn5cP-rubB_MM0g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Nov 9, 2019 at 3:58 PM Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> On 2019-11-08 14:38, Amit Kapila wrote:
> > I am planning to commit and backpatch this till PG10 where it was
> > introduced on Monday morning (IST). Pavel agreed that this is a good
> > change in the other thread where we need it [1]. It is not an urgent
> > thing, so I can wait if we think this is not a good time to commit
> > this. Let me know if anyone has objections?
>
> I think the change makes sense for master, but I don't think it should
> be backpatched.
>

Fair enough. Attached patch with a proposed commit message.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Attachment Content-Type Size
rearrange_countdbsubscription_check_2.patch application/octet-stream 2.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Eugen Konkov 2019-11-09 12:10:13 Re: Does 'instead of delete' trigger support modification of OLD
Previous Message Eugen Konkov 2019-11-09 12:05:02 Re: Does 'instead of delete' trigger support modification of OLD