m>>,
"pgsql-general@postgresql.org<mailto:pgsql-general@postgresql.org>"
mailto:pgsql-general@postgresql.org>>
Subject: Re: [GENERAL] Best practices for cloning DB servers
Thanks for the responses. Bill - We currently use wal-e to upload our WAL logs
to S3. We actu
Thanks for the responses. Bill - We currently use wal-e to upload our WAL
logs to S3. We actually don't keep our logs around for that long, so we
don't have a problem with the size of our logs or snapshots.
I think we're going to go with our current solution, but during our process
of cloning, poi
Why don't you try using Barman? It allows you to take snapshots and do
PITR. Not to mention you can use it as it's intended purpose as a backup
engine.
-Joseph
On Thu, Aug 14, 2014 at 1:53 PM, Bill Mitchell wrote:
> We are running our own Postgres server on AWS as well (since amazon RDS
> does
We are running our own Postgres server on AWS as well (since amazon RDS doesn't
support read replicas yet)
In out case, simply having a streaming replication standby works - and we do
our pg_dump from that -- or simply snapshot the machine and then promote the
replica to master to use full data
