Re: Unknown winsock error 10061

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Tsutomu Yamada <tsutomu(at)sraoss(dot)co(dot)jp>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Unknown winsock error 10061
Date: 2009-07-08 15:37:25
Message-ID: 937d27e10907080837q624b3927s9d8b6c2b755570a6@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jul 8, 2009 at 2:03 PM, Tsutomu Yamada<tsutomu(at)sraoss(dot)co(dot)jp> wrote:

> In the past, there was the thread about this problem,
> and it suggested using VirtualAllocEx().
> (But no patch was posted, right?)
> http://archives.postgresql.org/pgsql-general/2007-08/msg01592.php
>
> So I tries using VirtualAllocEx().
> By this fix, the problem doesn't occur in testing by pgbench.
>
> However, I cannot explain why the memory region was changed,
> and cannot guarantee that all problems are solved.

Ooh, interesting. I put a patched build at
http://uploads.enterprisedb.com/download.php?file=abb85b99acc1cf1668e3ff35bdb665ee

It has DEBUG_VQ defined. Wojciech - can you give it a try please?

Thanks Yamada-san.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-07-08 15:43:22 Re: pgstat wait timeout
Previous Message Robert Schnabel 2009-07-08 15:13:45 pgstat wait timeout