From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-hackers@lists.postgresql.org, Manuel Rigger <rigger.manuel@gmail.com>
Subject: Re: Broken defenses against dropping a partitioning column
Date: Mon, 22 Jul 2019 17:17:15 -0400
Message-ID: <19063.1563830235@sss.pgh.pa.us> (raw)
In-Reply-To: <20190722193459.GA14241@alvherre.pgsql>
References: <20190722193459.GA14241@alvherre.pgsql>
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2019-Jul-22, Tom Lane wrote:
>> I nearly missed the need for that because of all the noise that
>> check-world emits in pre-v12 branches. We'd discussed back-patching
>> eb9812f27 at the time, and I think now it's tested enough that doing
>> so is low risk (or at least, lower risk than the risk of not seeing
>> a failure). So I think I'll go do that now.
> I'd like that, as it bites me too, thanks.
Done. The approach "make check-world >/dev/null" now emits the
same amount of noise on all branches, ie just
NOTICE: database "regression" does not exist, skipping
The amount of parallelism you can apply is still pretty
branch-dependent, unfortunately.
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, alvherre@2ndquadrant.com, rigger.manuel@gmail.com
Subject: Re: Broken defenses against dropping a partitioning column
In-Reply-To: <19063.1563830235@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