Re: On partitioning
| От | Amit Kapila |
|---|---|
| Тема | Re: On partitioning |
| Дата | |
| Msg-id | CAA4eK1KoJyoV0qOd0a8rEj+iTiAb1ki0pVz5S8Zoi98pCKrDhg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: On partitioning (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: On partitioning
Re: On partitioning |
| Список | pgsql-hackers |
On Fri, Dec 5, 2014 at 10:03 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Tue, Dec 2, 2014 at 10:43 PM, Amit Langote
> <Langote_Amit_f8@lab.ntt.co.jp> wrote:
>
> > I wonder if your suggestion of pg_node_tree plays well here. This then could be a list of CONSTs or some such... And I am thinking it's a concern only for range partitions, no? (that is, a multicolumn partition key)
>
> I guess you could list or hash partition on multiple columns, too.
> On Tue, Dec 2, 2014 at 10:43 PM, Amit Langote
> <Langote_Amit_f8@lab.ntt.co.jp> wrote:
>
> > I wonder if your suggestion of pg_node_tree plays well here. This then could be a list of CONSTs or some such... And I am thinking it's a concern only for range partitions, no? (that is, a multicolumn partition key)
>
> I guess you could list or hash partition on multiple columns, too.
How would you distinguish values in list partition for multiple
columns? I mean for range partition, we are sure there will
be either one value for each column, but for list it could
be multiple and not fixed for each partition, so I think it will not
be easy to support the multicolumn partition key for list
partitions.
В списке pgsql-hackers по дате отправления: