Re: BUG #8451: quantile extension: memory corruption? - Mailing list pgsql-bugs

From Tomas Vondra
Subject Re: BUG #8451: quantile extension: memory corruption?
Date
Msg-id 523654EE.7000806@fuzzy.cz
Whole thread Raw
In response to Re: BUG #8451: quantile extension: memory corruption?  (Tomas Vondra <tv@fuzzy.cz>)
List pgsql-bugs
On 14.9.2013 14:12, Tomas Vondra wrote:
> On 13.9.2013 18:07, stephane.wustner@lip6.fr wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference:      8451
>> Logged by:          strexxx
>> Email address:      stephane.wustner@lip6.fr
>> PostgreSQL version: 9.1.9
>> Operating system:   Linux 3.8.0-27-generic #40-Ubuntu SMP x86_64
>> Description:
>>
>> A query such as this one
>> COPY (SELECT e,quantile(EXTRACT(EPOCH
>> FROM(d)),ARRAY[0,0.1,0.2,0.3,0.4,0.5,0.6,0.7,0.8,0.9,1]) AS d FROM (SELECT
>> e,max(time)-min(time) AS d FROM bb RIGHT JOIN (SELECT s,e FROM ss RIGHT JOIN
>> (SELECT e FROM ee WHERE h ~* 'blah') AS i0 USING(e)) AS i0  USING
>> (sessionid) GROUP BY e,ei) AS i1 GROUP BY e) TO 'full_path/d.csv' WITH
>> CSV;"
>
> Hi,
>
> this seems like a bug in the "quantile" extension, which is developed
> and distributed completely separately from PostgreSQL. So pgsql-bugs is
> not the right place to report the issue.
>
> I reported the issue on github and I'll look into that today/tomorrow
>
>    https://github.com/tvondra/quantile/issues/4
>
> so far it seems like a trivial bug in handling NULL values.

And indeed it was a bug in handling NULL values - the PG_ARGISNULL
happened too late. I plan to do few more improvements before pushing new
version to pgxn, but you may grab the sources from github directly.

Tomas

pgsql-bugs by date:

Previous
From: andrew@tao11.riddles.org.uk
Date:
Subject: BUG #8453: uninitialized memory access in pg_receivexlog and other bugs
Next
From: prakash_panda@yahoo.com
Date:
Subject: BUG #8454: Process returned exit 0 message is showing while taking backup