Re: Postgres Backup Utility

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Bradley Holbrook <operations_bradley(at)servillian(dot)ca>
Cc: "'Scott Marlowe'" <scott(dot)marlowe(at)gmail(dot)com>, "'French, Martin'" <frenchm(at)cromwell(dot)co(dot)uk>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Postgres Backup Utility
Date: 2011-01-22 18:22:45
Message-ID: A24D0F0F-A4DB-4958-83DB-AFBCEB9DE85D@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Jan 20, 2011, at 10:42 AM, Bradley Holbrook wrote:

> Martin French is right though, ask your developers to write down all their
> SQL struct changes and they look at you funny... and being a developer
> myself I'd look at me funny.

Well, it's what I do and it's trivial. Just don't type DDL directly into a psql session, edit it in your favorite text editor, in a document called updates-pending.sql, and copy & paste into psql. Sometimes a tiny bit of *process* can actually help productivity ;-)

--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2011-01-22 19:34:16 Re: Should autovacuum do a database wide vacuum near transaction limit?
Previous Message John Lister 2011-01-22 12:13:25 Re: Should autovacuum do a database wide vacuum near transaction limit?