| From: | Boxuan Zhai <bxzhai2010(at)gmail(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: MERGE Specification |
| Date: | 2010-08-11 04:18:18 |
| Message-ID: | AANLkTins2ok9tq4Wim2bK3WwpQjnR1qhVA-NU8Y90VSO@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 11, 2010 at 12:14 PM, Greg Smith <greg(at)2ndquadrant(dot)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.
>
> --
> Greg Smith 2ndQuadrant US Baltimore, MD
> PostgreSQL Training, Services and Support
> greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us <http://www.2ndquadrant.us/>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2010-08-11 04:34:05 | Re: Patch to show individual statement latencies in pgbench output |
| Previous Message | Greg Smith | 2010-08-11 04:14:44 | Re: MERGE Specification |