From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Hubert Lubaczewski <depesz(at)depesz(dot)com>, pgsql-hackers mailing list <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: explain analyze output with parallel workers - question about meaning of information for explain.depesz.com |
Date: | 2017-11-28 16:12:47 |
Message-ID: | CA+Tgmob0DqZJnwP_28TCqGHNNKAB_2cTNDp=2bUbkTBFeMSwDA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 28, 2017 at 2:23 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> That is wrong and I think you have hit a bug. It should be 2974 * 5 =
> 14870 as you have seen in other cases. The problem is that during
> rescan, we generally reinitialize the required state, but we forgot to
> reinitialize the instrumentation related memory which is used in the
> accumulation of stats, so changing that would fix some part of this
> problem which is that at Parallel node, you won't see wrong values.
> However, we also need to ensure that the per-worker details also get
> accumulated across rescans. Attached patch should fix the problem you
> are seeing. I think this needs some more analysis and testing to see
> if everything works in the desired way.
>
> Is it possible for you to test the attached patch and see if you are
> still seeing any unexpected values?
FWIW, this looks sensible to me. Not sure if there's any good way to
write a regression test for it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2017-11-28 16:16:46 | Re: [PATCH] Atomic pgrename on Windows |
Previous Message | Alexander Korotkov | 2017-11-28 16:11:05 | Re: [PATCH] Atomic pgrename on Windows |