Re: Fail to connect after server crash - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Fail to connect after server crash
Date
Msg-id dcc563d10801040909o31b7474ga1901fd809a82557@mail.gmail.com
Whole thread Raw
In response to Fail to connect after server crash  (Kyle Wilcox <Kyle.Wilcox@noaa.gov>)
Responses Re: Fail to connect after server crash  (Kyle Wilcox <Kyle.Wilcox@noaa.gov>)
List pgsql-general
Like Jonathan pointed out, looks like a permission issue.  We see
these things show up on Windows boxes quite often when a virus checker
/ spyware checker kicks in and does something stupid like lock a file
that postgresql needs to have exclusive access to.

Simple answer there is to put postgresql on it's own machine with no
spyware detection / anti-virus software on it, or more complexly, tell
it to ignore the directories where postgresql lives.

pgsql-general by date:

Previous
From: "beer@cmu.edu"
Date:
Subject: data volume resizing and large objects
Next
From: Kyle Wilcox
Date:
Subject: Re: Fail to connect after server crash