"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> On 9/5/06, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>> Magnus Hagander wrote:
>>> What do you mean by this? It doesn't start upon reboot? What is needed
>>> to make it start?
>>
>> It means that postgresql doesn't recover on its own. On linux if a
>> backend crashes all of PostgreSQL will restart and come back up if it can.
>>
>> On Win32 it doesn't.
> it does for me, at least for me when I used to work with windows :).
> I think it just doesn't restart for this particular type of crash.
As best I can tell, Josh isn't describing a crash at all. Something
(possibly in the TCP stack) has locked up, but there's no way for the
postmaster to know there's anything wrong, and probably no way for the
postmaster to fix it if it did know. Restarting backends certainly
isn't going to fix a communication problem.
Josh failed to answer the most important question though:
>> Subsequent connections to the database will fail (such as pgAdmin)
>> and Windows must be completely rebooted.
>
> Fail in what way. Hang, not connect, or get an error msg?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
