Re: Parallel append plan instability/randomness

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jim Finnerty <jfinnert(at)amazon(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel append plan instability/randomness
Date: 2018-01-08 20:05:25
Message-ID: CA+Tgmoaho8_QinAxEbKQ0UCHdK9VpnZvYLCfrs2R=3UHQqN+ug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 8, 2018 at 1:26 PM, Jim Finnerty <jfinnert(at)amazon(dot)com> wrote:
> I see. Maybe the EXPLAIN output can be made more stable when "EXPLAIN (costs
> FALSE)", though?

I think that would be fixing the problem from the wrong end. We want
to actually get a stable choice of plan, not display something other
than the actual plan because that other thing is more stable.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-01-08 20:27:35 Re: Condition variable live lock
Previous Message Tom Lane 2018-01-08 19:50:27 Re: Parallel append plan instability/randomness