OK, it is clear to me that I didn't make the best choices setting up this database. :(
I am happy I found this list because I am learning a lot in a very short period of time. :) Thank you all for your tips
andcomments.
I will definitely move the database to a Linux-system and set fsync to on. I hope this will give me a more stable
environment. Furthermore I'll dive into the whole database-backup subject so next time I'll have something to restore
ifthings go wrong.
Rob Goethals.
> -----Oorspronkelijk bericht-----
> Van: Albe Laurenz [mailto:laurenz.albe@wien.gv.at]
> Verzonden: maandag 17 februari 2014 16:20
> Aan: Rob Goethals
> CC: 'pgsql-general@postgresql.org'
> Onderwerp: RE: could not create lock file postmaster.pid: No such file or
> directory, but file does exist
>
> Rob Goethals wrote:
> > OK, clear. I hereby send this reply also to the list.
>
> Cool.
>
> >> Interesting.
> >> How did you get PostgreSQL into this state? Did you set fsync=off or
> similar?
> >> Which storage did you put pg_xlog on?
>
> > 2014-02-15 00:49:04 CET LOG: WAL writer process (PID 1127) was
> > terminated by signal 6: Aborted
>
> Ouch.
>
> > Furthermore I checked my conf-file and my fsync is indeed set to off.
>
> Well, that is one reason why crash recovery is not working.
>
> > I mounted a directory on a NTFS network-disk (because of the available
> > size and considering the amount of OSM-data is pretty big). This is where I
> put all my database data, so also the pg_xlog.
>
> Double ouch.
> CIFS is not a supported file system.
>
> At least that explains your problems.
> Try with a local file system or NFS with hard foreground mount.
>
> Yours,
> Laurenz Albe
