On Wed, Jul 8, 2009 at 2:03 PM, Tsutomu Yamada<tsut...@sraoss.co.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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
