Re: Auto Partitioning
| От | NikhilS |
|---|---|
| Тема | Re: Auto Partitioning |
| Дата | |
| Msg-id | d3c4af540704040619p6c99ee25q120f3edad5210c5e@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Auto Partitioning (Markus Schiltknecht <markus@bluegap.ch>) |
| Ответы |
Re: Auto Partitioning
Re: Auto Partitioning |
| Список | pgsql-hackers |
Hi,
Thanks Markus.
When I submitted the proposal, AFAIR there was no objection to going with the first proposal. Yes there was a lot of forward looking discussion, but since what I had proposed (atleast syntax wise) was similar/closer to Mysql, Oracle I did not see any one objecting to it. I think SQL server provides partitioning functions similar to Simon's proposal. And all along, I had maintained that I wanted to automate as far as possible, the existing mechanism for partitioning. To this too, I do not remember anyone objecting to.
Our current partitioning solution is based on inheritance. With that in mind, for 8.3 I thought an implementation based on auto rules creation would be the way to go.
Having said that, obviously I would want to go with the consensus on this list as to what we think is the *best* way to go forward with partitioning.
Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com
I appreciate you efforts, but I'm not sure if this has been discussed
Thanks Markus.
enough. There seem to be two ideas floating around:
- you are heading for automating the current kludge, which involves
creating partitions and constraints by hand. AFAICT, you want to
support list and range partitioning.
- Simon Riggs has proposed partitioning functions, which could easily
handle any type of partitioning (hash, list, range and any mix of
those).
When I submitted the proposal, AFAIR there was no objection to going with the first proposal. Yes there was a lot of forward looking discussion, but since what I had proposed (atleast syntax wise) was similar/closer to Mysql, Oracle I did not see any one objecting to it. I think SQL server provides partitioning functions similar to Simon's proposal. And all along, I had maintained that I wanted to automate as far as possible, the existing mechanism for partitioning. To this too, I do not remember anyone objecting to.
Our current partitioning solution is based on inheritance. With that in mind, for 8.3 I thought an implementation based on auto rules creation would be the way to go.
Having said that, obviously I would want to go with the consensus on this list as to what we think is the *best* way to go forward with partitioning.
Nikhils
--
EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: