Re: explain analyze rows=%.0f

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com>, Andrei Lepikhov <lepihov(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: explain analyze rows=%.0f
Date: 2025-02-22 00:04:31
Message-ID: 3737950.1740182671@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Well, not quite yet, at least. There are two buildfarm failures since
> I committed this. The first is here:

A very significant fraction of the buildfarm is now pink.
If you don't have a fix pretty nearly ready, please revert.

> I imagine what happened here is that the parallel workers didn't
> start, and so nloops was 1 instead of >1, and so we got an integer
> output instead of a fractional one.

Sounds plausible. I note that this run:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skimmer&dt=2025-02-21%2023%3A00%3A10

got through a couple of iterations of the core tests before failing,
showing that it's not 100% reproducible even on the machines where
it's happening.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2025-02-22 00:30:17 Re: GetRelationPath() vs critical sections
Previous Message Michael Paquier 2025-02-21 23:50:03 Re: Missing [NO] INDENT flag in XMLSerialize backward parsing