Re: [HACKERS] hash partitioning based on v10Beta2

Поиск
Список
Период
Сортировка
Искать
От
yangjie
Тема
Re: [HACKERS] hash partitioning based on v10Beta2
Дата
Msg-id
A4CDB3DF-0FF1-4211-B808-5E3C0A958A0C@highgo.com
Ответ на
Список
Дерево обсуждения
[HACKERS] hash partitioning based on v10Beta2 "yangjie@highgo.com" <yangjie@highgo.com>
Re: [HACKERS] hash partitioning based on v10Beta2 "yangjie@highgo.com" <yangjie@highgo.com>
Re: [HACKERS] hash partitioning based on v10Beta2 Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] hash partitioning based on v10Beta2 yangjie <yangjie@highgo.com>
Re: [HACKERS] hash partitioning based on v10Beta2 Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] hash partitioning based on v10Beta2 Rushabh Lathia <rushabh.lathia@gmail.com>
Hi,

When the number of partitions and the data are more, adding new partitions, there will be some efficiency problems.
I don't know how the solution you're talking about is how to implement a hash partition?

---

young

HighGo Database: http://www.highgo.com


On 8/28/2017 22:25Robert Haas<robertmhaas@gmail.com> wrote:
On Sat, Aug 26, 2017 at 12:40 AM, yangjie@highgo.com <yangjie@highgo.com> wrote:
> A partition table can be create as bellow:
>
>  CREATE TABLE h1 PARTITION OF h;
>  CREATE TABLE h2 PARTITION OF h;
>  CREATE TABLE h3 PARTITION OF h;

This syntax is very problematic for reasons that have been discussed
on the existing hash partitioning thread.  Fortunately, a solution has
already been implemented... you're the third person to try to write a
patch for this feature.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
От: Robert Haas
Дата:
FAQ