From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rui Hai Jiang <ruihaij@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: TopoSort() fix
Date: Tue, 02 Jul 2019 11:23:30 -0400
Message-ID: <12243.1562081010@sss.pgh.pa.us> (raw)
In-Reply-To: <CAEri+mLd3bpHLyW+a9pSe1y=aEkeuJpwBSwvo-+m4n7-ceRmXw@mail.gmail.com>
References: <CAEri+mLd3bpHLyW+a9pSe1y=aEkeuJpwBSwvo-+m4n7-ceRmXw@mail.gmail.com>
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?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, ruihaij@gmail.com, robertmhaas@gmail.com
Subject: Re: TopoSort() fix
In-Reply-To: <12243.1562081010@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox