From: | Martin Moore <martin(dot)moore(at)avbrief(dot)com> |
---|---|
To: | rob stone <floriparob(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres 9.6 fails to start on VMWare |
Date: | 2017-10-23 08:14:18 |
Message-ID: | EB707CC3-1D6F-4EB1-8334-1234B83A02DD@avbrief.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Same server. I tried a few times.
I didn’t move the db separately, but did a ‘dd’ to copy the disk to an imagefile which was converted and loaded into VMWare.
I ‘believed’ that this should keep the low level disk structure the same, but if this has corrupted the files I can drop, dump and restore, in which case how do I ‘drop’ the DB without postgres running?
Ta,
Martin.
On 23/10/2017, 00:51, "rob stone" <floriparob(at)gmail(dot)com> wrote:
On Sun, 2017-10-22 at 15:13 +0100, Martin Moore wrote:
> 2017-10-22 14:08:28 UTC [2479-1] LOG: 00000: database system
> shutdown was interrupted; last known up at 2017-10-22 14:07:20 UTC
There is something missing here. Last shutdown at 2017-10-22 14:07:20
UTC on which server?
Then attempting to start it at 2017-10-22 14:08:28 UTC? One minute and
eight seconds later.
It might also help if you explained exactly how you moved the database
from Google Compute to this VM machine.
Cheers,
robert
From | Date | Subject | |
---|---|---|---|
Next Message | Popov Aleksey | 2017-10-23 13:06:07 | Matching statement and duration log lines |
Previous Message | Juliano | 2017-10-23 07:45:07 | Re: Alternative to pgAdmin Postgres Manager that support pgagent (jobs) |