Re: Using JIT for VACUUM, COPY, ANALYZE

From: Andres Freund <andres(at)anarazel(dot)de>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>,PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: Using JIT for VACUUM, COPY, ANALYZE
Date: 2018-03-11 19:38:54
Message-ID: A860AE10-F86D-4B87-9A34-AC7A0B53E71D@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On March 11, 2018 12:31:33 PM PDT, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>Hi
>
>Today, these task can be CPU limited . Do you think, so JIT can be used
>there too?

Copy definitely, with the others I'm much more doubtful. Don't see anything around their bottlenecks that could be removed by JITing. Haven't looked at profiles of them recently however.

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2018-03-11 19:41:40 Re: Parallel index creation does not properly cleanup after error
Previous Message Greg Stark 2018-03-11 19:36:09 Re: Sample values for pg_stat_statements