Replacing a production db

From: Nicolás Lichtmaier <nico(dot)lichtmaier(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Replacing a production db
Date: 2014-06-18 20:05:22
Message-ID: CA+MknoCF7vWX6kfMeSN9TS7+qdegJKVa2siOOMAsY_gBM=5XeA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Is there a way to replace a production database with another as part of a
new "release" of our website?

Where I work we have a scheme of pushing code+db releases to "testing" and
then to "production". Most of our databases use MySQL and I was told they
can just rename the db and it works. We are adopting PostgreSQL for some
new developments and we'd like to do something similar. I've tried loading
the dump in a single transaction, but that has many problems as the
database is fairly big for that (some GBs). Is there a trick I'm missing
here?

Thanks a lot!

Nicolás.-

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Sullivan 2014-06-18 20:37:07 Re: Replacing a production db
Previous Message Kevin Grittner 2014-06-18 18:58:14 Re: Troubles with Postgresql performance