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-11T19:54:13Z

Lists: pgsql-hackers

On Mon, Feb 11, 2019 at 11:46 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I think we're done with this thread, though I still need to look at
> the problem I complained of in <26527.1549572789@sss.pgh.pa.us>.

Right, we're done with this thread now. Thanks again!

-- 
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