Re: making EXPLAIN extensible - Mailing list pgsql-hackers

From Robert Haas
Subject Re: making EXPLAIN extensible
Date
Msg-id CA+Tgmoa5Dny+FWv6_fa4oaedyVCk4VYR9by6QfMaXDgDenVqsA@mail.gmail.com
Whole thread Raw
In response to Re: making EXPLAIN extensible  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: making EXPLAIN extensible
List pgsql-hackers
On Wed, Mar 26, 2025 at 10:40 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > -         ->  Index Scan using daucus_id_idx on daucus v2_2 (actual
> > rows=0.12 loops=8)
> > +         ->  Index Scan using daucus_id_idx on daucus v2_2 (actual
> > rows=0.13 loops=8)
>
> Even if this had not failed in the buildfarm, it would certainly
> have caused problems for somebody. We have a very strong rule
> that you *do not* make regression test results dependent on exact
> computed cost or rowcount values, because those are inherently
> platform-dependent.  I do not understand how you thought that
> pg_overexplain might be exempt from that problem.

Is this rule written down someplace?

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Ilia Evdokimov
Date:
Subject: Re: Remove vardata parameters from eqjoinsel_inner
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: Draft for basic NUMA observability