Jeff Janes,
Ok. I checked this further and just found that the pg_xlog area is
symlinked to another area.. and indeed that other area was not being
rsynced (!) and I thought it was. So, I just fixed this, re-ran it and
now it is working. Now I believe I have a stable postgres running on M2.
On Tue, May 31, 2016 at 10:13 AM, Jim Longwill wrote:
> I am trying to setup a 2nd, identical, db server (M2) for development and
> I've run into a problem with starting up the 2nd Postgres installation.
>
> Here's what I've done:
> 1) did a 'clone' of 1st (production) machine M1 (so both machin
Scott,
Thanks. If I understand you correctly.. Actually, we did have M1
shutdown when the inital clone was done (some weeks ago). That was done
using the VMWare system, not rsync. My main problem is that I don't
have WAL archiving setup yet (I've not changed the Postgres defaults on
this
On Wed, Jun 1, 2016 at 3:13 AM, Jim Longwill wrote:
> I am trying to setup a 2nd, identical, db server (M2) for development and
> I've run into a problem with starting up the 2nd Postgres installation.
>
> Here's what I've done:
> 1) did a 'clone' of 1st (production) machine M1 (so both machine
On Tuesday, May 31, 2016 10:13:14 AM Jim Longwill wrote:
> I am trying to setup a 2nd, identical, db server (M2) for development
> and I've run into a problem with starting up the 2nd Postgres installation.
>
> Here's what I've done:
>1) did a 'clone' of 1st (production) machine M1 (so both ma
On Tue, May 31, 2016 at 1:13 PM, Jim Longwill wrote:
> I am trying to setup a 2nd, identical, db server (M2) for development and
> I've run into a problem with starting up the 2nd Postgres installation.
>
> Here's what I've done:
> 1) did a 'clone' of 1st (production) machine M1 (so both machin
