At pgday there was this form you could fill to give speakers some feedback about their talks. And that’s a really nice way as a speaker to know what to improve. And as Magnus was searching a nice looking chart facility in python and I spoke about matplotlib, it felt like having to publish something.
Here is my try at some nice graphics. Well I’ll let you decide how nice the result is:
I wrote a book!
So there it is, this newer contribution of mine that I presented at PGDay is now in debian NEW queue. pg_staging will empower you with respect to what you do about those nightly backups ( pg_dump -Fc or something).
The tool provides a lot of commands to either dump or restore a database. It comes with documentation covering about it all, except for the londiste support part, which will be there in time for 1.
moment. Lots of attendees, lots of quality talks ( slides are online), good food, great party: all the ingredients were there!
It also was for me the occasion to first talk about this tool I’ve been working on for months, called pg_staging, which aims to empower those boring production backups to help maintaining staging environments (for your developers and testers).
All in all such events keep reminding me what it means exactly when we way that one of the greatest things about PostgreSQL is its community.
As you might have noticed, this little blog of mine is not compromising much and entirely maintained from Emacs. Until today, I had to resort to term to upload my publications, though, as I’ve been too lazy to hack up the tools integration for simply doing a single rsync command line. That was one time to many:
(defvar dim:muse-rsync-options "-avz" "rsync options") (defvar dim:muse-rsync-source "~/dev/muse/out" "local path from where to rsync, with no ending /") (defvar dim:muse-rsync-target "dim@tapoueh.
So there it is, at long last, the final 1.0.0 release of prefix! It’s on its way into the debian repository (targetting sid, in testing in 10 days) and available on pgfoundry to.
In order to make it clear that I intend to maintain this version, the number has 3 digits rather than 2… which is also what PostgreSQL users will expect.
The only last minute change is that you can now use the first version of the two following rather than the second one:
So you have a rolodex like database in your Emacs, or you have this phone number in a mail and you want to call it. It happens you have VoIP setup and you’re using Twinkle to make your calls. Maybe you’ll then find this function useful:
(defun twinkle-call-symbol-or-region () "Call the phone number at point (symbol seems good enough), or in region" (interactive) (shell-command-to-string (format "twinkle --cmd 'call %s'" (replace-regexp-in-string "[^0-9+]" "" (if (use-region-p) (buffer-substring (region-beginning) (region-end)) (thing-at-point 'symbol)))))) It happens that symbol is better than word here because some phone numbers begin with +.