Re: Updating a production database schema from dev server

From: mljv(at)planwerk6(dot)de
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Updating a production database schema from dev server
Date: 2008-01-04 09:08:03
Message-ID: 200801041008.03582.mljv@planwerk6.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

try using liquibase. http://www.liquibase.org/ . It works very well.

kind regards,
Janning

Am Dienstag, 16. Oktober 2007 18:38 schrieb Stanislav Raskin:
> Hello everybody,
>
>
>
> I am currently running two PostgreSQL servers on two different machines.
> One of them I use for development and the other one as the "real"
> production server for my applications.
>
> While developing new versions of these applications, I of course have to
> modify the database schema, including changing the definitions of views and
> sql functions, creating new indexes and removing others, changing schemas
> and data types in some tables, redistributing privileges and so on. Until
> now, when I decided to update the applications on the production machine to
> a newer version, I used to apply these changes manually, which is quite
> error-prone and annoying.
>
> I figure there must be a better way to do so. Is there some kind of
> software, which compares two database schemas (preferably two sql dumps),
> and generates a script for applying differences to one of them?
>
> What would be the best practice for applying such updates without
> endangering the data and its integrity?
>
>
>
> Thank you very much in advance.
>
>
>
> SR

--
kind regards,
janning

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ivan Sergio Borgonovo 2008-01-04 09:31:30 Solution: implicit vs. explicit RETURN when OUT is used
Previous Message Steve Atkins 2008-01-04 09:03:52 Re: server process (PID 27884) was terminated by signal 4 (SIGILL)