--- Patrick Samson wrote:
> If I run a test script enough time, it eventually
> freezes in this deadlock situation:
> The client sends a command to a backend and waits
> for an answer. It will wait forever because the
> is not aware of the arrival of the request and waits
> for a next command.
> What happens in the loop is:
> SIInsertDataEntry: table is 70% full,
> signaling postmaster
> In reaction, the postmaster sends to its children:
> SignalChildren: sending signal 31 to process <pid>
> Most of the time, it works. But at an unpredictable
> iteration, it freezes.
> I can't tell if the source of the problem is in
> cygwin or in postgres, so I post in the two lists.
Nothing to say about Postgres, the problem is
located within Cygwin.
for the full story.
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
In response to
pgsql-cygwin by date
|Next:||From: Greg B. Hill||Date: 2004-03-31 17:47:19|
|Subject: Re: initdb error|
|Previous:||From: mike g||Date: 2004-03-31 04:19:24|
|Subject: Postgres crashing intermittentaly|