| From: | Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Windows XP to Win 10 migration issue |
| Date: | 2017-12-12 10:14:28 |
| Message-ID: | 3d40f5bc-44c0-df7d-a7a3-7067e5831bf4@evolu-s.it |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Il 11/12/2017 14:37, Vincent Veyron ha scritto:
> On Sat, 9 Dec 2017 10:11:42 -0600
> Dale Seaburg <kg5lt(at)verizon(dot)net> wrote:
>
>> No Go! Would not start.
> Any error message in your logs?
>
> I would certainly second Scott's suggestion to check the processors. I've had to do what you describe once, and it took me four machines before I got one that would start postgresql with my rescued data folder.
>
> You might have better luck finding an old XP machine similar to your deceased one, installing postgresql on it, and using that to start your cluster.
>
>
I'd take a peek into logs (maybe EventLog), it happened to me that the
postgres user in windows 10 did not have the permission to access data
directory. Setting the right permissions could make it start. Obviously
the processor architecture (32/64 bit) must be honored.
My 2 cent
| From | Date | Subject | |
|---|---|---|---|
| Next Message | marcelo | 2017-12-12 12:14:23 | Re: How to know if a database has changed |
| Previous Message | Yogesh Sharma | 2017-12-12 09:52:03 | Size of pg_multixact/members increases 11355 |