Re: Parallel append plan instability/randomness

From: Jim Finnerty <jfinnert(at)amazon(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Parallel append plan instability/randomness
Date: 2018-01-08 16:28:15
Message-ID: 1515428895102-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ordering the plan output elements by estimated cost will cause spurious plan
changes to be reported after table cardinalities change. Can we choose an
explain output order that is stable to changes in cardinality, please?

thank you,

/Jim

--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-01-08 16:36:08 Re: Parallel append plan instability/randomness
Previous Message Robert Haas 2018-01-08 16:27:40 Re: [HACKERS] Refactoring identifier checks to consistently use strcmp