Re: More stable query plans via more predictable column statistics - Mailing list pgsql-hackers

From Alex Shulgin
Subject Re: More stable query plans via more predictable column statistics
Date
Msg-id CAM-UEKT3UF=CFPym5WfzjOyaQLCJiP991PjfUP1GbDmhiyifng@mail.gmail.com
Whole thread Raw
In response to Re: More stable query plans via more predictable column statistics  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Apr 3, 2016, 18:40 Tom Lane <tgl@sss.pgh.pa.us> wrote:
Alex Shulgin <alex.shulgin@gmail.com> writes:

> Well, if it's the only value it will be accepted simply because we are
> checking that special case already and don't even bother to loop through
> the track list.

That was demonstrably not the case in the failing regression test.
I forget what aspect of the test case allowed it to get past the short
circuit, but it definitely got into the scan-the-track-list code.

Hm, I'll have to see that for myself, probably there was something more to it.

--
Alex

pgsql-hackers by date:

Previous
From: Alex Shulgin
Date:
Subject: Re: Add schema-qualified relnames in constraint error messages.
Next
From: Stephen Frost
Date:
Subject: Re: Proposal: RETURNING primary_key()