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

Re: Schema migration tools?

From: Erik Jones <erik(at)myemma(dot)com>
To: John DeSoi <desoi(at)pgedit(dot)com>
Cc: Christophe <xof(at)thebuild(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Schema migration tools?
Date: 2008-04-22 21:59:32
Message-ID: 007F3AD9-468D-4A13-ABB9-FC9B5658E0A5@myemma.com (view raw or flat)
Thread:
Lists: pgsql-general
On Apr 22, 2008, at 4:33 PM, John DeSoi wrote:

>
> On Apr 22, 2008, at 4:53 PM, Erik Jones wrote:
>
>>> It would be nice if PostgreSQL had some kind of unique reference  
>>> for the column, but I think columns are just numbered sequentially  
>>> as they are added. It would also be neat to have a built-in way to  
>>> log the schema changes.
>>
>> It does: log_statement set to either 'all' or 'ddl' will do the  
>> trick.
>
> If I do this, is there a way to get a transaction consistent log of  
> just the necessary commands to transform another copy of the  
> database? In other words, I assume this approach will log each DDL  
> command even if the transaction is rolled back. Correct?


Right.  It's not something you'd want to lift directly and run  
somewhere else.

Erik Jones

DBA | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com




In response to

Responses

pgsql-general by date

Next:From: Erik JonesDate: 2008-04-22 22:01:51
Subject: Re: Rapidly decaying performance repopulating a large table
Previous:From: David WilsonDate: 2008-04-22 21:46:42
Subject: Re: Rapidly decaying performance repopulating a large table

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