Re: [HACKERS] [POC] hash partitioning
| От | Robert Haas |
|---|---|
| Тема | Re: [HACKERS] [POC] hash partitioning |
| Дата | |
| Msg-id | CA+TgmoZOowOvB_S14LFoD0SzH980Ek1dkcbjkQK7-edKx4gkNA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] [POC] hash partitioning (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: [HACKERS] [POC] hash partitioning
|
| Список | pgsql-hackers |
On Thu, Oct 12, 2017 at 3:43 PM, Andres Freund <andres@anarazel.de> wrote: > Are we going to rely on the the combine function to stay the same > forever after? If we change them, it will be a pg_upgrade compatibility break for anyone using hash-partitioned tables with more than one partitioning column. Dump and reload will also break unless --load-via-partition-root is used. In other words, it's not utterly fixed in stone --- we invented --load-via-partition-root primarily to cope with circumstances that could change hash values --- but we sure don't want to be changing it with any regularity, or for a less-than-excellent reason. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: