From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
Subject: | Re: BitmapHeapScan streaming read user and prelim refactoring |
Date: | 2024-05-14 18:40:14 |
Message-ID: | CAAKRu_Y10u44mrkPjdnSdYZGUeQ-==quRhXypH7_O3Uy_c4_Nw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 14, 2024 at 2:33 PM Tomas Vondra
<tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
>
> On 5/14/24 19:42, Melanie Plageman wrote:
> > I've fixed this. I've also set enable_material off as I mentioned I
> > might in my earlier mail.
> >
>
> I'm not sure this (setting more and more GUCs to prevent hypothetical
> plan changes) is a good practice. Because how do you know the plan does
> not change for some other unexpected reason, possibly in the future?
Sure. So, you think it is better not to have enable_material = false?
> IMHO if the test requires a specific plan, it's better to do an actual
> "explain (rows off, costs off)" to check that.
When you say "rows off", do you mean do something to ensure that it
doesn't return tuples? Because I don't see a ROWS option for EXPLAIN
in the docs.
- Melanie
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2024-05-14 18:44:45 | Re: BitmapHeapScan streaming read user and prelim refactoring |
Previous Message | Robert Haas | 2024-05-14 18:35:20 | Re: libpq compression (part 3) |