Re: TopoSort() fix - Mailing list pgsql-hackers

From Robert Haas
Subject Re: TopoSort() fix
Date
Msg-id CA+TgmoYXVNU4VA_faderE6BXn-JE88V2-VeSRQ2zoVFkSMWmFA@mail.gmail.com
Whole thread Raw
In response to Re: TopoSort() fix  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: TopoSort() fix  (Rui Hai Jiang <ruihaij@gmail.com>)
List pgsql-hackers
On Tue, Jul 2, 2019 at 11:23 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Rui Hai Jiang <ruihaij@gmail.com> writes:
> > I think I found an issue in the TopoSort() function.
>
> This indeed seems like a live bug introduced by a1c1af2a.
> Robert?

This is pretty thoroughly swapped out of my head, but it looks like
that analysis might be correct.

Is it practical to come up with a test case that demonstrates the problem?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Anthony Nowocien
Date:
Subject: Re: Conflict handling for COPY FROM
Next
From: Tom Lane
Date:
Subject: Re: Another way to fix inherited UPDATE/DELETE