Postgres Pro
Downloads
Home   >   mailing lists

Re: REVOKE command not working as expected - Mailing list pgsql-admin

From Guillermo Carrasco
Subject Re: REVOKE command not working as expected
Date
Msg-id CAH-nkqngD+qCHeYJcjnxmDMd3qJyxS2+GFs+hhq6MWzsjpw4ZQ@mail.gmail.com
Whole thread Raw
In response to Re: REVOKE command not working as expected  (Scott Ribe <scott_ribe@elevated-dev.com>)
Responses Re: REVOKE command not working as expected  (Scott Ribe <scott_ribe@elevated-dev.com>)
List pgsql-admin
Tree view
Hi Scott,
We want to make an exact copy of production, even if someone have made changes in stage, we want to remove all the changes and leave stage as an exact copy of production, will pg_start_backup do the work?




On Tue, Nov 12, 2013 at 4:19 PM, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
Why not just shut down the staging server, pg_start_backup on production, and rsync the db???

On Nov 12, 2013, at 8:02 AM, Guillermo Carrasco <guillermo.carrasco@scilifelab.se> wrote:

> Thanks for your answer, I know, that's why we have this statement: https://github.com/guillermo-carrasco/scilifelab/blob/master/scripts/dbsync.sh#L20
>


--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice







--
------------------------------------------------------------------------
Guillermo Carrasco Hernández, Computer Scientist

------------------------------------------------------------------------

pgsql-admin by date:

Previous
From: Scott Ribe
Date:
Subject: Re: REVOKE command not working as expected
Next
From: Scott Ribe
Date:
Subject: Re: REVOKE command not working as expected