| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Multi-column distinctness. |
| Date: | 2015-10-20 00:16:03 |
| Message-ID: | 562587C3.4060105@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Kyotaro-san,
On 09/11/2015 06:58 PM, Tomas Vondra wrote:
>
> Maybe the best solution is to abandon the ALTER TABLE approach
> entirely, and instead invent a new set of commands
>
> CREATE STATISTICS
> DROP STATISTICS
>
> (ALTER STATISTICS seems a bit excessive at this point).
>
> Another thing is that perhaps we should add names for statistics,
> just like we do for constraints, for example. Otherwise the DROP
> STATISTICS handling is rather awkward - for example if the user
> creates stats twice by mistake, he's unable to drop just one of them.
Do you think this modified syntax makes sense? I'll have time to hack on
this over the next few days.
regards
--
Tomas Vondra http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-10-20 00:21:38 | Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |
| Previous Message | Tom Lane | 2015-10-20 00:12:31 | Re: Why no CONSTANT for row variables in plpgsql? |