Any suggestions for a topic?
Join or login to comment.
Interesting presentation. After reviewing the documentation, it seems like the partition keys need to be immutable in each row. Did I miss something about the triggers moving rows when the partition key is updated? In the region example at the presentation, as a company expands geographically, rows that at one time represented facilities in the North may become South. A company that begins life in southern Georgia may consider Atlanta "North" but later as a national company Atlanta might be considered "South". Later, as a global firm Atlanta may be in its "East" region. A row representing a customer in Atlanta may have to move between partitions as the company changes because of the table constraint. Would this be a problem? A database designer at a start-up may not be able to anticipate a partitioning key changing.
0 · December 14, 2012
I'm pretty sure that was covered, and the answer is: your partition keys should be immutable because partition migration is not supported. So, no, north cannot become south in your example. This is a fairly standard issue with any partitioning scheme. If you think you might need to rebalance data across partitions or move things, you have to figure out on your own how to deal with the partition migration issues or..."don't do that".
George, we talked briefly about partition migration at the end. It does require an insert into the new partition and a delete from the old one. Definitely important to choose your partitions carefully! In this case it might be possible to subpartition to a unit with is not as likely to be broken up, and then move that subpartition to the north partition.
Good presentation and Q&A session. There were several things about partitioning in Postgres that I simply did not know until last night. It was worth going to the Meetup just for that, but I also liked the demonstration of how you have automated the creation and maintenance of partitions. This could be a real time saver for anyone using partitioning!
One more note, if you are running late to the meetup, the building doors do lock at *7PM*. If you get here and they are locked, call my cell (info at http://async.io/postgresql_meetup.html) for access.
0 · December 13, 2012
INFORMATION ABOUT THE MEETUP LOCATION
So I promised more information about the location for the meetup tomorrow night. Apparently, I am not succinct enough to fit it into a Meetup message. So all the information about the meetup is available at
Let me know if you have any questions.
0 · December 12, 2012
Hi Denish, I will be giving the talk. Looking forward to it!
0 · December 8, 2012
Who is giving talk ?
0 · December 7, 2012
I think the building is still open at 6:30 so you can just come straight up to the UberOffices office on the 10th floor, but I will confirm that. However, I will send out more detailed information about entrances to the building, parking nearby, and getting to the building from Metro.
Looking forward to it. Any special instructions for getting into the building?
Next: Invite friends
A group of database technologists that discuss data technology of all types, but with a focus on the PostgreSQL relational database.
Open to developers, admins, and engineers of all types!
Meeting Space, Food & Drink
Hosting, Drinks, Food
1,427 Computational Linguists
1,813 Data Enthusiasts
4,580 Entrepreneurs and Startups
2,571 Android Fans
Meetup members, Log in