| From: | John DeSoi <desoi(at)pgedit(dot)com> |
|---|---|
| To: | Erik Jones <erik(at)myemma(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:33:32 |
| Message-ID: | 71252044-34DF-47BD-82E5-05A6E5D0E3BA@pgedit.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
Thanks,
John DeSoi, Ph.D.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | D. Dante Lorenso | 2008-04-22 21:34:55 | Re: How to modify ENUM datatypes? |
| Previous Message | Joshua D. Drake | 2008-04-22 21:28:22 | Re: How to modify ENUM datatypes? |