News for hackers. Stuff that matters.
Re:PostgreSQL partitioning explained by jeffdavis on Saturday May 03, 2014 @09:42PM (#7693026)
It probably will be. There are two primary reasons it hasn't happened yet (in my opinion):

1. It takes a while to get widespread agreement on the semantics to make sure it really solves the problem in a comprehensive way.

2. The existing mechanism is "good enough", so nobody is quite experiencing enough pain that they dedicate the effort to solve it.

These aren't great reasons, because other databases have had partitioning features for a long time. But they are reasons.

Re:PostgreSQL partitioning explained by clubhi on Saturday May 03, 2014 @10:59PM (#7693148)
I'm experiencing the pain. I've been championing postgres in my company for a couple of years now. The partitioning limitations have been quite embarrassing. It's not just the annoying lack of helper syntax to make partitioning better. It's the actual huge limitations on what the planner can consider when trying to find a derived table.
Re:PostgreSQL partitioning explained by twic on Sunday May 04, 2014 @06:10AM (#7693818)
What are the other contenders you are championing PostgreSQL against? How do they do at partitioning?
Re:PostgreSQL partitioning explained by aktau on Sunday May 04, 2014 @08:17AM (#7694023)
It pains me to say this, but when I was working with Oracle, its partitioning support was miles ahead of postgres (though not perfect by any stretch of the imagination).