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

From David Steele
Subject Re: More stable query plans via more predictable column statistics
Date
Msg-id 56D718D4.7090105@pgmasters.net
Whole thread Raw
In response to Re: More stable query plans via more predictable column statistics  ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>)
Responses Re: More stable query plans via more predictable column statistics  ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>)
List pgsql-hackers
On 3/2/16 11:10 AM, Shulgin, Oleksandr wrote:
> On Wed, Feb 24, 2016 at 12:30 AM, Tomas Vondra
> <tomas.vondra@2ndquadrant.com <mailto:tomas.vondra@2ndquadrant.com>> wrote:
>
>     I think it'd be useful not to have all the changes in one lump, but
>     structure this as a patch series with related changes in separate
>     chunks. I doubt we'd like to mix the changes in a single commit, and
>     it makes the reviews and reasoning easier. So those NULL-handling
>     fixes should be in one patch, the MCV patches in another one.
>
>
> OK, such a split would make sense to me.  Though, I'm a bit late as the
> commitfest is already closed to new patches, I guess asking the CF
> manager to split this might work (assuming I produce the patch files)?

If the patch is broken into two files that gives the review/committer
more options but I don't think it requires another CF entry.

--
-David
david@pgmasters.net


pgsql-hackers by date:

Previous
From: Thom Brown
Date:
Subject: Re: multivariate statistics v10
Next
From: Tomas Vondra
Date:
Subject: Re: multivariate statistics v10