Re: Proposal for syntax to support creation of partition tables whencreating parent table
От | Amit Langote |
---|---|
Тема | Re: Proposal for syntax to support creation of partition tables whencreating parent table |
Дата | |
Msg-id | CA+HiwqE5r=hfvjxBagkAstwiFfrfbqwtbU_Y_T5_1pgQGFLpjw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Proposal for syntax to support creation of partition tables whencreating parent table (Ahsan Hadi <ahsan.hadi@gmail.com>) |
Список | pgsql-hackers |
Hi Ahsan, Usama Thanks for starting work on this. On Thu, Sep 26, 2019 at 3:46 AM Ahsan Hadi <ahsan.hadi@gmail.com> wrote: > On Wed, Sep 25, 2019 at 8:53 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> As Fabien noted, there's been some related discussion about this >> area, but nobody was advocating a solution of this particular shape. > > The thread that Usama mentioned in his email is creating auto-partitions just for HASH partitions, this is trying to dosimilar for all types of partitions. I agree that this proposal makes life easier for developers familiar with the partitioning syntax and features of other databases. However, it adds little functionality over what users can already do, even though today it takes multiple commands rather than just one. The problem is that the syntax proposed here is still verbose because users still have to spell out all the partition bounds by themselves. The focus of the other thread, as I understand it, is to implement the functionality to get the same thing done (create many partitions in one command) in much less verbose manner. Fabien started the discussion for hash partitioning because the interface for it seems straightforward -- just specify the number of partitions and that many partitions would get created without having to actually specify modulus/remainder for each. Since the underlying functionality wouldn't be too different for other partitioning methods, we would only have to come up with a suitable interface. Thanks, Amit
В списке pgsql-hackers по дате отправления: