From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: multivariate statistics v8 |
Date: | 2016-01-20 19:20:38 |
Message-ID: | CA+TgmoZjZT69k9ZcA73kqa4FES8wiJUJSf3hTeCc0YXV5ARpeA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 23, 2015 at 2:07 PM, Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> The remaining question is how unique the statistics name should be.
> My initial plan was to make it unique within a table, but that of
> course does not work well with the DROP STATISTICS (it'd have to
> specify the table name also), and it'd also now work with statistics
> on multiple tables (which is one of the reasons for abandoning ALTER
> TABLE stuff).
>
> So I think it should be unique across tables. Statistics are hardly
> a global object, so it should be unique within a schema. I thought
> that simply using the schema of the table would work, but that of
> course breaks with multiple tables in different schemas. So the only
> solution seems to be explicit schema for statistics.
That solution seems good to me.
(with apologies for not having looked at the rest of this much at all)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2016-01-20 19:26:38 | Re: Releasing in September |
Previous Message | Andres Freund | 2016-01-20 19:13:51 | Re: Releasing in September |