Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages)

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages)
Date: 2019-02-11 20:04:45
Message-ID: 20190211200445.GA30250@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-Feb-11, Tom Lane wrote:

> I've pushed this now. I made one additional change, which was to fix
> things so that if both an INTERNAL and an EXTENSION dependency exist,
> the first loop will reliably complain about the EXTENSION dependency.
> It only takes one more if-test to do that now that we're postponing
> the error report till after the loop, and this way we don't need to
> split hairs about how likely it is for both to exist.
>
> I think we're done with this thread, though I still need to look at
> the problem I complained of in <26527(dot)1549572789(at)sss(dot)pgh(dot)pa(dot)us>.

Thanks for taking care of this!

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Flower 2019-02-11 20:29:48 Re: [Patch] Log10 and hyperbolic functions for SQL:2016 compliance
Previous Message Peter Geoghegan 2019-02-11 19:54:13 Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages)