On Wed, Aug 11, 2010 at 12:18 PM, Boxuan Zhai <bxzhai2...@gmail.com> wrote:
> > > On Wed, Aug 11, 2010 at 12:14 PM, Greg Smith <g...@2ndquadrant.com>wrote: > >> Boxuan Zhai wrote: >> >>> I just found that no Assert() works in my codes. I think it is because >>> the assertion is no enabled. How to enable assertion. To define >>> USE_ASSERT_CHECKING somewhere? >>> >> >> When you run "configure" before "make", use "--enable-cassert". The >> normal trio for working on the PostgreSQL code is: >> >> ./configure --enable-depend --enable-cassert --enable-debug >> >> Generally the only reason to build as a developer without asserts on is to >> do performance testing. They will slow some portions of the code down >> significantly. >> >> > Thanks. I will test MERGE under this new configuration. A new patch will be > submitted once I fix all the asserting bugs. > >> >> The new patch is done. I named it as merge_v102. (1 means it is the non-inheritance merge command, 02 means this is the second time of fixing reported bugs) > -- >> Greg Smith 2ndQuadrant US Baltimore, MD >> PostgreSQL Training, Services and Support >> g...@2ndquadrant.com www.2ndQuadrant.us <http://www.2ndquadrant.us/> >> >> >
merge_v102.tar.gz
Description: GNU Zip compressed data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
