| From: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: More stable query plans via more predictable column statistics |
| Date: | 2016-03-03 07:48:29 |
| Message-ID: | CACACo5SUovv4oXAeo_7CyeSdumGCZ0k-0BknvQfSU8d1KM1L9g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 2, 2016 at 7:33 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:
> Shulgin, Oleksandr wrote:
>
> > Alright. I'm attaching the latest version of this patch split in two
> > parts: the first one is NULLs-related bugfix and the second is the
> > "improvement" part, which applies on top of the first one.
>
> So is this null-related bugfix supposed to be backpatched? (I assume
> it's not because it's very likely to change existing plans).
>
For the good, because cardinality estimations will be more accurate in
these cases, so yes I would expect it to be back-patchable.
--
Alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-03-03 07:58:54 | Re: Dockerfile for testing with Perl 5.8.8 |
| Previous Message | Andres Freund | 2016-03-03 07:47:27 | Re: Confusing with commit time usage in logical decoding |