So as promised - the patch is very stable. No more memory problems, neither any other issues.
Great job Yamada-san!!!! Dave - can I assume you'll manage this fix to be pushed to official release? On 9 Lip, 17:08, wstrzalka <wstrza...@gmail.com> wrote: > Looks very good by now. > > I'll test the version for a few days in my regular work and will > post more feedback here. > > On 8 Lip, 17:37, dp...@pgadmin.org (Dave Page) wrote: > > > 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 > > athttp://uploads.enterprisedb.com/download.php?file=abb85b99acc1cf1668e... > > > 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-b...@postgresql.org) > > To make changes to your > > subscription:http://www.postgresql.org/mailpref/pgsql-bugs -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
