| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
| Subject: | Re: embedded list v2 |
| Date: | 2012-09-28 23:54:37 |
| Message-ID: | 18107.1348876477@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On Saturday, September 29, 2012 01:39:03 AM Tom Lane wrote:
>> 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.
Eh? You would anyway, or at least recompile every .o file depending on
that header, if what you want is to inline or de-inline the functions.
There's no magic shortcut for that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-29 00:13:44 | Re: Generalizing range-constraint detection in clauselist_selectivity |
| Previous Message | Josh Berkus | 2012-09-28 23:54:13 | Re: Generalizing range-constraint detection in clauselist_selectivity |