Skip site navigation (1) Skip section navigation (2)

Re: Postgres Backup Utility

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: "French, Martin" <frenchm(at)cromwell(dot)co(dot)uk>
Cc: Bradley Holbrook <operations_bradley(at)servillian(dot)ca>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Postgres Backup Utility
Date: 2011-01-20 16:21:09
Message-ID: AANLkTi=Sx8GvOz+DGNarMxpXrdktg8YWvLb0y2c2Ekd5@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Thu, Jan 20, 2011 at 8:46 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Thu, Jan 20, 2011 at 5:00 AM, French, Martin <frenchm(at)cromwell(dot)co(dot)uk> wrote:
>
>>  Personally, I'd rather
>> not go trawling through what can only be described as hundreds of
>> thousands of lines of PostgreSQL log to find THE RIGHT DDL statements.
>
> Oh that's easy.  Grep out the statements that start with alter etc,
> ptu them all in a big email, send them to all the developers and tell
> them to let you know which ones need applying to QA / Staging / etc.
> Can't get your DDL to the DBA?  Your code won't work.  You break the
> build because of that, you get to fix it.

Note that I also mentioned turning on logging JUST ddl statements.
Assumiing you're not logging EVERYTHING in development (and why would
you) you should only have a few dozen lines of log to grep, and little
or none of it will be things other than DDL.
-- 
To understand recursion, one must first understand recursion.

In response to

pgsql-admin by date

Next:From: CS DBADate: 2011-01-20 16:53:02
Subject: State of multi-master replication options
Previous:From: Scott MarloweDate: 2011-01-20 15:46:04
Subject: Re: Postgres Backup Utility

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group