From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Rui Hai Jiang <ruihaij@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: TopoSort() fix
Date: Mon, 29 Jul 2019 10:56:05 -0400
Message-ID: <23797.1564412165@sss.pgh.pa.us> (raw)
In-Reply-To: <20190729015059.GE6959@paquier.xyz>
References: <CAEri+mKtZkj=+phnkkD9_8sf1fLFUqwHio8Ls4f7JGVgqku6QQ@mail.gmail.com>
<20190726220538.GA17809@alvherre.pgsql>
<20190726234835.xqyfukqhhzdiqoih@alap3.anarazel.de>
<17997.1564187056@sss.pgh.pa.us>
<20190729015059.GE6959@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> On Fri, Jul 26, 2019 at 08:24:16PM -0400, Tom Lane wrote:
>> I think this is a sufficiently obvious bug, and a sufficiently
>> obvious fix, that we should just fix it and not insist on getting
>> a reproducible test case first. I think a test case would soon
>> bit-rot anyway, and no longer exercise the problem.
>> I certainly do *not* want to wait so long that we miss the
>> upcoming minor releases.
> +1. Any volunteers?
If Robert doesn't weigh in pretty soon, I'll take responsibility for it.
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, michael@paquier.xyz, andres@anarazel.de, alvherre@2ndquadrant.com, ruihaij@gmail.com, robertmhaas@gmail.com
Subject: Re: TopoSort() fix
In-Reply-To: <23797.1564412165@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