| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Instability of partition_prune regression test results |
| Date: | 2019-09-27 15:59:03 |
| Message-ID: | 11381.1569599943@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> On Fri, Sep 27, 2019 at 7:25 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I experimented with adjusting explain_parallel_append() to filter
>> more fields, but soon realized that we'd have to filter out basically
>> everything that makes it useful to run EXPLAIN ANALYZE at all.
>> Therefore, I think it's time to give up this testing methodology
>> as a bad idea, and fall back to the time-honored way of running a
>> plain EXPLAIN and then the actual query, as per the attached patch.
> Isn't the point of using ANALYZE here to show that the exec-param
> based run-time pruning is working (those "never executed" strings)?
Hm. Well, if you want to see those, we could do it as attached.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| change-parallel-append-testing-2.patch | text/x-diff | 21.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Asif Rehman | 2019-09-27 16:00:01 | Re: WIP/PoC for parallel backup |
| Previous Message | Fujii Masao | 2019-09-27 15:58:02 | Re: Standby accepts recovery_target_timeline setting? |