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

Peter Geoghegan <pg@bowt.ie>

From: Peter Geoghegan <pg@bowt.ie>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2019-02-08T02:53:34Z

Lists: pgsql-hackers

On Wed, Feb 6, 2019 at 9:15 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I have a mostly-working patch along these lines that I hope to
> finish up and post tomorrow.

Do you think that you'll end up pushing the HEAD-only fix shortly? It
would be nice to avoid immediate bitrot of an upcoming revision of the
nbtree patch series.

Thanks
-- 
Peter Geoghegan

Commits

Redesign the partition dependency mechanism.
- 1d92a0c9f7dd 12.0 landed
Fix trigger drop procedure
- cc126b45ea5c 11.2 landed
- cb90de1aac18 12.0 landed
Sort the dependent objects before recursing in findDependentObjects().
- f1ad067fc3ae 12.0 landed
Avoid sometimes printing both tables and their columns in DROP CASCADE.
- 9194c4270b28 12.0 landed