On Fri, May 24, 2019 at 4:18 PM Tom Lane wrote:
> Yes, I see that too with sufficiently high -j. I believe this is
> what Noah was trying to fix in bd1592e85, but that patch evidently
> needs a bit more work :-(
It would be nice if this was fixed, but I don't see a problem when I
use the optimum
Peter Geoghegan writes:
> My development machine has 8 logical cores, and like you I only see
> the NOTICE from pg_upgrade's tests with "-j10":
> pg@bat:/code/postgresql/patch/build$ time make check-world -j10 >/dev/null
> NOTICE: database "regression" does not exist, skipping
> make check-world
On Fri, May 24, 2019 at 12:31 PM Peter Geoghegan wrote:
>
> On Wed, May 22, 2019 at 3:57 PM Tom Lane wrote:
> > I experimented with the attached quick-hack patch to make pg_regress
> > suppress notices from its various initial DROP/CREATE IF [NOT] EXISTS
> > commands. I'm not entirely convinced
On Wed, May 22, 2019 at 3:57 PM Tom Lane wrote:
> I experimented with the attached quick-hack patch to make pg_regress
> suppress notices from its various initial DROP/CREATE IF [NOT] EXISTS
> commands. I'm not entirely convinced whether suppressing them is
> a good idea though. Perhaps some hac
[ redirected from a thread in pgsql-committers[1] ]
As of commit eb9812f27 you can run a manual check-world with
stdout dumped to /dev/null, and get fairly clean results:
$ time make check-world -j10 >/dev/null
NOTICE: database "regression" does not exist, skipping
real1m43.875s
user2m5
