If you don't remember about what
pg_staging is all about, it's a central
console from where to control all your
PostgreSQL databases. Typically you
use it to manage your development and pre-production setup, where developers
ask you pretty often to install them some newer dump from the production,
and you want that operation streamlined and easy.
Hannu just gave me a good idea in
this email on
-hackers, proposing that
pg_basebackup should get the
xlog files again and again in a loop for the
whole duration of the
base backup. That's now done in the aforementioned
tool, whose options got a little more useful now:
These days, thanks to my
community oriented job, I'm working full time on a
PostgreSQL patch to terminate basic support for
extending SQL. First thing I
want to share is that patching the
backend code is not as hard as one would
think. Second one is that
git really is helping.
This year's edition has been the
best pgcon ever for me. Granted, it's only
my third time, but still :) As
Josh said the
"Hall Track" in particular was
very good, and the
Dev Meeting has been very effective!
So there it is, this newer contribution of mine that I presented at
debian NEW queue.
pg_staging will empower you with respect to what
you do about those nightly backups (
pg_dump -Fc or something).
moment. Lots of
attendees, lots of quality talks (
slides are online), good
food, great party: all the ingredients were there!