- Logical Changeset Generation, the basis for the new replication;
- Setting postgresql.conf variables from the SQL command line;
- Transaction Log size autotuning;
- Row-Level Security;
- GIN Fast Scan, and other GIN index improvements;
- Block-based range indexes for very large tables;
- Concurrent update of materialized views;
- Multiple pgbench enhancements;
- Many performance improvements;
- A bunch of additional regression tests.
If you want to help, but aren't sure what to review, please join the pgsql-rrreviewers mailing list and announce yourself there. I will assign you a patch to review.
For those of you who are experienced reviewers or who have submitted a patch to this CommitFest, please note the following:
- If you submitted a patch to this CommitFest, you are expected to review at least one other person's patch. Should you choose not to do so, the community will not be obligated to guarantee you a review of your patch.
- If you put your name down as a reviewer on a patch, and you don't post anything for 5 days, we will send you a reminder and take your name off the patch, to prevent you from blocking other reviewers.
- If your patch goes to "waiting on author" and you don't respond for 5 days, the patch will be Returned with Feedback.
No time wasted!!ReplyDelete
The links to the patches work on www.databasesoup.com, but not from planet.postgresql.org (looks like an extra url encoding).
Yeah, I can't do anything about that.Delete
And the transparent table partitioning was left alone in the corner again. Maybe in the 10.0 version... :(ReplyDelete
Nobody is, AFAIK, working on that. If it's important to you, then maybe you should be -- either hacking, or fundraising.Delete
Josh, unfortunatly I don't have skills to hack and I don't have money to fundraising this because I think that is a huge work.ReplyDelete
What I'm talking about is that core team sometimes does not pay attention to certain "must have" features, like a simple form to do a table partitioning. But ok. I will continue to pray to see this in the future. ;)
It's on the TODO list. But we're a community project; we don't have a large pool of full-time developers able to work on whatever they please. Doing better partitioning would require, I'd estimate, a full-time developer for at least a year, so it's not something anyone can do "in their spare time". So if it really matters to you, find a way to help make it happen.Delete