| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 11:29:51 |
| Message-ID: | CA+Tgmoa5Dny+FWv6_fa4oaedyVCk4VYR9by6QfMaXDgDenVqsA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 26, 2025 at 10:40 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
Is this rule written down someplace?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nazir Bilal Yavuz | 2025-03-27 11:30:48 | Re: Draft for basic NUMA observability |
| Previous Message | Ilia Evdokimov | 2025-03-27 11:00:30 | Re: Remove vardata parameters from eqjoinsel_inner |