Re: making EXPLAIN extensible - Mailing list pgsql-hackers

From Tom Lane
Subject Re: making EXPLAIN extensible
Date
Msg-id 1814753.1743043232@sss.pgh.pa.us
Whole thread Raw
In response to Re: making EXPLAIN extensible  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: making EXPLAIN extensible
List pgsql-hackers
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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Ajin Cherian
Date:
Subject: Re: Historic snapshot doesn't track txns committed in BUILDING_SNAPSHOT state
Next
From: Tom Lane
Date:
Subject: Re: Add Postgres module info