Re: Multi-column distinctness. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Multi-column distinctness.
Date
Msg-id 33010.1445356773@sss.pgh.pa.us
Whole thread Raw
In response to Re: Multi-column distinctness.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Multi-column distinctness.  (Simon Riggs <simon@2ndQuadrant.com>)
Re: Multi-column distinctness.  (Robert Haas <robertmhaas@gmail.com>)
Re: Multi-column distinctness.  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Oct 20, 2015 at 10:51 AM, Tomas Vondra
> <tomas.vondra@2ndquadrant.com> wrote:
>>>> ISTM that we could use COLLECT STATISTICS instead of ADD STATISTICS, and
>>>> use REMOVE STATISTICS instead of DROP STATISTICS. That way we can use
>>>> ALTER TABLE rather than inventing a new command. 5 minute change...

>> That seems like a neat idea, actually. I'm not sure COLLECT is a good choice
>> as it suggest the statistics is actually built, but that only happens during
>> ANALYZE. But otherwise this seems to solve the issues with keywords and it's
>> quite simple.

> But ADD is no better there.  I think ALTER TABLE .. COLLECT STATISTICS
> isn't any worse than ALTER TABLE ... CLUSTER ON index_name.  In both
> cases, it means, when you do this operation, do it this way.

> I would suggest that instead of DROP or REMOVE, the opposite should be
> ALTER TABLE .. NO COLLECT STATISTICS.

Why is this an improvement over using already-existing keywords?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [PATCH] SQL function to report log message
Next
From: CharSyam
Date:
Subject: [PATCH] Typos in comments