From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | Tels <nospam-pg-abuse(at)bloodgate(dot)com>, Stephen Froehlich <s(dot)froehlich(at)cablelabs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Subject: | Re: STATISTICS retained in CREATE TABLE ... LIKE (INCLUDING ALL)? |
Date: | 2018-01-27 23:00:26 |
Message-ID: | 0f0b1ae8-fd18-486c-8153-d7daea7a90c5@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-novice |
On 01/27/2018 10:45 PM, Tom Lane wrote:
> David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
>> I'd offer to put it back to the order of the enum, but I want to
>> minimise the invasiveness of the patch. I'm not sure yet if it should
>> be classed as a bug fix or a new feature.
>
> FWIW, I'd call it a new feature.
>
I'm not sure what exactly the feature would be? I mean "keep statistics
even if you only ask for indexes" does not seem particularly helpful to
me. So I see it more like a bug - I certainly think it should have been
handled differently in 10.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2018-01-27 23:01:20 | Re: \describe* |
Previous Message | Tomas Vondra | 2018-01-27 22:55:33 | Re: STATISTICS retained in CREATE TABLE ... LIKE (INCLUDING ALL)? |
From | Date | Subject | |
---|---|---|---|
Next Message | Dav Clark | 2018-01-28 18:39:24 | Using the pgadmin4 packages |
Previous Message | Tomas Vondra | 2018-01-27 22:55:33 | Re: STATISTICS retained in CREATE TABLE ... LIKE (INCLUDING ALL)? |