Re: Partitioning option for COPY

Tom Lane wrote:
> A good rule of thumb is to never do code development in a non-cassert
> build. 
And the same rule goes for review, too; I'll update the review 
guidelines to spell that out more clearly.  Basically, if you're doing 
any work on new code, you should have cassert turned on, *except* if 
you're doing performance testing.  The asserts slow things down enough 
(particularly with large shared_buffers values) to skew performance 
tests, but in all other coding situations you should have them enabled.

-- 
Greg Smith    2ndQuadrant   Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com  www.2ndQuadrant.com