If you’ve not been following closely you might have missed out on extensions integration. Well, Tom spent some time on the patches I’ve been preparing for the last 4 months. And not only did he commit most of the work but he also enhanced some parts of the code (better factoring) and basically finished it.
At the previous developer meeting his advice was to avoid putting too much into the very first version of the patch for it to stand its chances of being integrated, and while in the review process more than one major PostgreSQL contributor expressed worries about the size of the patch and the number of features proposed.
I wrote a book!
This year we were in the main building of the conference, and apparently the booth went very well, solding lots of PostgreSQL merchandise etc. I had the pleasure to once again meet with the community, but being there only 1 day I didn’t spend as much time as I would have liked with some of the people there.
In case you’re wondering, my extension’s talk went quite well, and several people were kind enough to tell me they appreciated it!
A quick blog entry to say that yes:
And I will even do my Extension’s talk which had a success at pgday.eu. The talk will be updated to include the last developments of the extension’s feature, as some of it changed already in between, and to detail the plan for the ALTER EXTENSION ... UPGRADE feature that I’d like to see included as soon as 9.1, but time is running so fast.
It so happens that a colleague of mine wanted to start using Emacs but couldn’t get to it. He insists on having proper color themes in all applications and some sensible defaults full of nifty add-ons everywhere, and didn’t want to have to learn that much about Emacs and Emacs Lisp to get started. I’m not even sure that he will Take the Emacs tour.
You would tell me that there’s nothing we can do for so unfriendly users.
Yes, you read it well, el-get currently features 174 recipes, and is now reaching the 1.1 release. The reason for this release is mainly that I have two big chunks of code to review and the current code has been very stable for awhile. It seems better to do a release with the stable code that exists now before to shake it this much. If you’re wondering when to jump in the water and switch to using el-get, now is a pretty good time.
You certainly know that implementing dynamic triggers in PLpgSQL is impossible. But I had a very bad night, being up from as soon as 3:30 am today, so that when a developer asked me about reusing the same trigger function code from more than one table and for a dynamic column name, I didn’t remember about it being impossible.
Here’s what happens in such cases, after a long time on the problem (yes, overall, that’s a slow day).