Prev: [COMMITTERS] pgsql: Add missing optimizer hooks for function cost and number of rows.
Next: don't allow walsender to consume superuser_reserved_connection slots, or during shutdown
From: Andrew Dunstan on 23 Apr 2010 20:09 Xiong He wrote: > When I build the debug version of PostgreSQL (latest code), I found > that I always failed to > run the vcregress.bat check. It always pops up the following error. > The release version can pass the test without any error. > > Anyone met such error? > [graphic deleted] Please don't send pictures to the list. Send text of error messages. You will need to dig down much more to find out exactly what triggers the error. You haven't even told us which regression set you are running, let alone which test it fails on. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "=?utf-8?B?WGlvbmcgSGU=?=" on 23 Apr 2010 20:19
Thanks. In my test, it fails during the vcregress.bat check startup. It's a Debug Assertion Error. File: dbgheap.c Line: 1252. E:\learn\db_research\postgreSQL\cvsroot\pgsql.latest\src\tools\msvc>vcregress.ba t check No test can run. I used VS2005 for the build. Xiong He 2010-04-24 08:15:04 åä»¶äººï¼ Andrew Dunstan åéæ¶é´ï¼ 2010-04-24 08:09:32 æ¶ä»¶äººï¼ Xiong He æéï¼ pgsql-hackers 主é¢ï¼ Re: [HACKERS] vcregress.bat check triggered Heap error in the Debugversion of win32 build Xiong He wrote: > When I build the debug version of PostgreSQL (latest code), I found > that I always failed to > run the vcregress.bat check. It always pops up the following error. > The release version can pass the test without any error. > > Anyone met such error? > [graphic deleted] Please don't send pictures to the list. Send text of error messages. You will need to dig down much more to find out exactly what triggers the error. You haven't even told us which regression set you are running, let alone which test it fails on. cheers andrew |