Hi,
On 2018-07-30 13:31:33 -0400, Jeff Janes wrote:
> I don't know where the time is going with the as-committed JIT. None of
> the JIT-specific timings reported by EXPLAIN (ANALYZE) add up to anything
> close to the slow-down I'm seeing. Shouldn't compiling and optimization
> time show up there
Hi,
On 2018-07-30 18:01:34 +0200, Pavel Stehule wrote:
> look on
> http://www.postgresql-archive.org/PATCH-LLVM-tuple-deforming-improvements-td6029385.html
> thread, please.
Given the results I just posted in the sibling email I don't think those
issues apply here.
Greetings,
Andres Freund
On Mon, Jul 30, 2018 at 12:01 PM, Pavel Stehule
wrote:
>
>
> 2018-07-30 13:19 GMT+02:00 Jeff Janes :
>
>> On Mon, Jul 30, 2018 at 12:11 AM, Pavel Stehule
>> wrote:
>>
>>> 2018-07-30 1:00 GMT+02:00 Tom Lane :
>>>
David Rowley writes:
> On 29 July 2018 at 17:38, Dinesh Kumar wrote:
>>>
On 2018-07-30 07:19:07 -0400, Jeff Janes wrote:
> On Mon, Jul 30, 2018 at 12:11 AM, Pavel Stehule
> wrote:
>
> > 2018-07-30 1:00 GMT+02:00 Tom Lane :
> >
> >> David Rowley writes:
> >> > On 29 July 2018 at 17:38, Dinesh Kumar wrote:
> >> >> I found performance variance between accessing int1 an
2018-07-30 13:19 GMT+02:00 Jeff Janes :
> On Mon, Jul 30, 2018 at 12:11 AM, Pavel Stehule
> wrote:
>
>> 2018-07-30 1:00 GMT+02:00 Tom Lane :
>>
>>> David Rowley writes:
>>> > On 29 July 2018 at 17:38, Dinesh Kumar wrote:
>>> >> I found performance variance between accessing int1 and int200 colu
On Mon, Jul 30, 2018 at 12:11 AM, Pavel Stehule
wrote:
> 2018-07-30 1:00 GMT+02:00 Tom Lane :
>
>> David Rowley writes:
>> > On 29 July 2018 at 17:38, Dinesh Kumar wrote:
>> >> I found performance variance between accessing int1 and int200 column
>> which
>> >> is quite large.
>>
>> > Have a lo
