Re: embedded list v2 - Mailing list pgsql-hackers

From Andres Freund
Subject Re: embedded list v2
Date
Msg-id 201209290142.50065.andres@2ndquadrant.com
Whole thread Raw
In response to Re: embedded list v2  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: embedded list v2
List pgsql-hackers
On Saturday, September 29, 2012 01:39:03 AM Tom Lane wrote:
> Andres Freund <andres@2ndquadrant.com> writes:
> > The reason I had the header declare DEFINE_ILIST_FUNCTIONS (or rather
> > ILIST_USE_DEFINITION back then) instead of reusing USE_INLINE directly is
> > that it makes it easier to locally change a "module" to not inlining
> > which makes testing the !USE_INLINE case easier. Does anybody think this
> > is worth something? I have no strong feelings but found it convenient.
> 
> Right offhand it doesn't seem like it really gains that much even for
> that use-case.  You'd end up editing the include file either way, just
> slightly differently.
Well, with USE_INLINE you have to recompile the whole backend because you 
otherwise easily end up with strange incompatibilities between files.

Andres
-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: embedded list v2
Next
From: Josh Berkus
Date:
Subject: Re: Generalizing range-constraint detection in clauselist_selectivity