From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Add documentation for the JIT feature. |
Date: | 2018-03-31 15:32:01 |
Message-ID: | 9b31f912-fb14-6218-5211-5dde627b9b17@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 3/29/18 14:43, Alvaro Herrera wrote:
>> Hm, what's wrong just doing it in the normal build? It's a desired build
>> artifact, so I really don't see any argument for not building it by
>> default? Don't quite see what the advantage of doing it during make
>> check would be?
> I meant running something that would check that the file compiles,
> without actually producing the output. For the regular docs, there's a
> couple of orders of magnitude of difference in time to do the check vs.
> the actual build.
Or we do both.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-03-31 15:43:37 | Re: pgsql: Add documentation for the JIT feature. |
Previous Message | Fabien COELHO | 2018-03-31 07:00:02 | Re: pgsql: Set random seed for pgbench. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2018-03-31 15:38:54 | Re: Online enabling of checksums |
Previous Message | Tom Lane | 2018-03-31 15:25:23 | Re: WIP: a way forward on bootstrap data |