On Wed, Jan 20, 2016 at 02:20:38PM -0500, Robert Haas wrote: > On Wed, Dec 23, 2015 at 2:07 PM, Tomas Vondra > <tomas.von...@2ndquadrant.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)
Woh, this will be an optimizer game-changer, from the user perspective! -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
