Re: Stored procedure version control

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Stored procedure version control
Date: 2016-07-02 00:22:50
Message-ID: 5777095A.20203@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 07/01/2016 06:17 PM, Jim Nasby wrote:
> On 6/30/16 9:16 AM, Merlin Moncure wrote:
>> It's not really necessary to create version down scripts. In five
>> years of managing complex database environments we've never had to
>> roll a version back and likely never will; in the event of a disaster
>> it's probably better to restore from backup anyways.
>
> I'm surprised no one has mentioned http://sqitch.org. It makes it very
> easy to manage migrations, as well as creating downgrade scripts (if
> you use rework, and put each object into it's own file).
>
> I do agree that down scripts are pretty over-rated as long as you have
> good test practices (as in, database unit tests). In 9 years in an
> environment where downtime was 6 figures per hour I only had 1 or 2
> deployments that had problems, and never bad enough to consider
> reverting.
I've found down scripts quite useful in development. One does have to
know how to neuter them on the way to production however.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Karsten Hilbert 2016-07-02 12:19:34 Re: Stored procedure version control
Previous Message Jim Nasby 2016-07-02 00:17:06 Re: Stored procedure version control