Re: Duplicate Workers entries in some EXPLAIN plans

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Maciek Sakrejda <maciek(at)pganalyze(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Duplicate Workers entries in some EXPLAIN plans
Date: 2019-10-22 05:34:53
Message-ID: 941.1571722493@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Maciek Sakrejda <maciek(at)pganalyze(dot)com> writes:
> Should I move this to a pgsql-hackers discussion? I noticed that jsonb also
> appears to keep the last JSON entry in the face of multiple keys, so it'd
> be nice to have something more usable. I'm not much of a C programmer, but
> I think I see how to rename the second fields to Sort Workers if this
> solution is acceptable.

Yeah, the actual code change should be pretty trivial --- the hard part
here is to get consensus on what behavior change we want. It's not
unreasonable to decide that on pgsql-bugs ... but since there hasn't
been much commentary yet, maybe moving to -hackers is what to do
to seek consensus.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Gilleain Torrance 2019-10-22 09:25:37 RE: Incorrect rounding of double values at max precision
Previous Message Maciek Sakrejda 2019-10-22 05:29:32 Re: Duplicate Workers entries in some EXPLAIN plans