Tome Lane wrote: Theory B is that you've got some broken antivirus code on there that is arbitrarily interfering with the pipe access. The lack of any similar previous reports suggests that there's some local issue contributing ,,,
Steve Marshall wrote: To explore Theory B, I'll turned off all non-essential services on the Windows server and rerun the test. This included turning of Symantec AV and several other services we don't use anyway. The test turned out exactly the same: one of the events was dropped from pg_listener within a few seconds of starting the test. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
