Re: pg_listener entries deleted under heavy NOTIFY load only on Windows

From: "Marshall, Steve" <smarshall(at)wsi(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_listener entries deleted under heavy NOTIFY load only on Windows
Date: 2009-01-20 14:02:15
Message-ID: 4975D967.1070805@wsi.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="mid20090116142201(dot)GD9963(at)alvh(dot)no-ip(dot)org" type="cite">
<pre wrap="">Marshall, Steve wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Any thoughts on how to confirm or deny Theory A?
</pre>
</blockquote>
<pre wrap=""><!---->Alvaro Herrera wrote:
Try changing the 1000 to NMPWAIT_WAIT_FOREVER
</pre>
</blockquote>
I'd tried Alvaro suggestion and it fixed the problem in my test case.&nbsp;
With the original code, the test would consistantly drop one of the
events from pg_listener within a few seconds.&nbsp; With the changed
timeout, I've run it for about 10 minutes, or 100,000 notifications of
each event, and it worked without error.<br>
<br>
Are there any side effects from effectively disabling this timeout that
should be tested?<br>
<br>
<br>
</body>
</html>

Attachment Content-Type Size
unknown_filename text/html 1.0 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2009-01-20 14:51:16 Re: [BUGS] BUG #4186: set lc_messages does not work
Previous Message Hiroshi Inoue 2009-01-20 03:52:12 Re: [BUGS] BUG #4186: set lc_messages does not work