| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JIT compiling with LLVM v9.0 |
| Date: | 2018-02-01 13:46:08 |
| Message-ID: | 147a6148-bf4a-a149-ae2a-66a587eb09c4@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/31/18 14:45, Robert Haas wrote:
> We could do that, but I'd be more inclined just to let JIT be
> magically enabled. In general, if a user could do 'yum install ip4r'
> (for example) and have that Just Work without any further database
> configuration,
One way to do that would be to have a system-wide configuration file
like /usr/local/pgsql/etc/postgresql/postgresql.conf, which in turn
includes /usr/local/pgsql/etc/postgresql/postgreql.conf.d/*, and have
the add-on package install its configuration file with the setting jit =
on there.
Then again, if we want to make it simpler, just link the whole thing in
and turn it on by default and be done with it.
Presumably, there will be planner-level knobs to model the jit startup
time, and if you don't like it, you can set that very high to disable
it. So we don't necessarily need a separate turn-it-off-it's-broken
setting.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-02-01 13:54:08 | Re: ALTER TABLE ADD COLUMN fast default |
| Previous Message | Peter Eisentraut | 2018-02-01 13:42:35 | Re: JIT compiling with LLVM v9.0 |