From: | Patrick Samson <p_samson(at)yahoo(dot)com> |
---|---|
To: | pgsql-cygwin(at)postgresql(dot)org |
Subject: | Re: Backend doesn't catch the next command, after SIGUSR2 |
Date: | 2004-03-31 06:54:22 |
Message-ID: | 20040331065422.66786.qmail@web60310.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cygwin |
--- 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
> backend
> 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.
Look at
http://cygwin.com/ml/cygwin/2004-03/msg00418.html
for the full story.
__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html
From | Date | Subject | |
---|---|---|---|
Next Message | Greg B. Hill | 2004-03-31 17:47:19 | Re: initdb error |
Previous Message | mike g | 2004-03-31 04:19:24 | Postgres crashing intermittentaly |