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 and comments.
I will definitely move the database to a Linux-system and set fsync to on.
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 term
Rob Goethals / SNP writes:
> When it is trying to startup again this is the logfile output:
> ...
> 2014-02-15 00:50:05 CET PANIC: could not create file
> "pg_xlog/xlogtemp.5390": Input/output error
The above PANIC is the reason for the abort that happens immediately
thereafter.
On local stor
On 17 February 2014 14:42, Rob Goethals / SNP wrote:
> 2014-02-15 00:49:04 CET LOG: WAL writer process (PID 1127) was terminated
> by signal 6: Aborted
Signal 6 is usually caused by hardware issues.
Then again, you also say:
>I mounted a directory on a NTFS network-disk (because of the avail
> -Oorspronkelijk bericht-
> Van: Albe Laurenz [mailto:laurenz.a...@wien.gv.at]
> Verzonden: maandag 17 februari 2014 14:22
> Aan: Rob Goethals
> Onderwerp: RE: could not create lock file postmaster.pid: No such file or
> directory, but file does exist
>
> Dear Rob,
>
> you should send
Rob Goethals wrote:
> This is my first post to this list, so I hope I am posting it to the correct
> lists. But I am really
> stuck and getting pretty desperate at the moment.
You should not post to more than one list.
> This weekend my database crashed while importing some Openstreetmapdata and
