Replacing a production db - Mailing list pgsql-general

From Nicolás Lichtmaier
Subject Replacing a production db
Date
Msg-id CA+MknoCF7vWX6kfMeSN9TS7+qdegJKVa2siOOMAsY_gBM=5XeA@mail.gmail.com
Whole thread Raw
Responses Re: Replacing a production db
Re: Replacing a production db
Re: Replacing a production db
Re: Replacing a production db
List 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.-

pgsql-general by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: Troubles with Postgresql performance
Next
From: Andrew Sullivan
Date:
Subject: Re: Replacing a production db