OK. What if we do not need to access the static data on the test volume? It
is a rare application that goes there, and for those we can bring over both
volumes/tablespaces.
Thx, ken
On Fri, Feb 8, 2013 at 10:09 PM, Gavan Schneider wrote:
> On Friday, February 8, 2013 at 10:58, Tom Lane wrote:
>
On Friday, February 8, 2013 at 10:58, Tom Lane wrote:
If it breaks you get to keep both pieces.
Tom is an optimist. My (unscheduled) attempt at this resulted in
a lot more than two pieces all of which appeared broken in their
own right.
If you want to (re)start a conversation about making
Kenneth Tilton writes:
> Currently we refresh our test DB instance by cloning the single production
> EC2 volume we use for our entire PG environment and attaching it to the dev
> EC2 instance running Postgres. This works well.
> But now we are about to add a large quantity of largely static data
Currently we refresh our test DB instance by cloning the single production
EC2 volume we use for our entire PG environment and attaching it to the dev
EC2 instance running Postgres. This works well.
But now we are about to add a large quantity of largely static data to our
database. To avoid cloni
