| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrei Lepikhov <lepihov(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: making EXPLAIN extensible |
| Date: | 2025-03-27 02:40:32 |
| Message-ID: | 1814753.1743043232@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:
> - -> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-27 02:45:22 | Re: Add Postgres module info |
| Previous Message | Ajin Cherian | 2025-03-27 02:30:32 | Re: Historic snapshot doesn't track txns committed in BUILDING_SNAPSHOT state |