Re: Parallel append plan instability/randomness - Mailing list pgsql-hackers

From Jim Finnerty
Subject Re: Parallel append plan instability/randomness
Date
Msg-id 1515428895102-0.post@n3.nabble.com
Whole thread Raw
In response to Re: Parallel append plan instability/randomness  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Parallel append plan instability/randomness
Re: Parallel append plan instability/randomness
List 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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Refactoring identifier checks to consistently use strcmp
Next
From: Robert Haas
Date:
Subject: Re: Parallel append plan instability/randomness