Re: Performance of aggregates over set-returning functions - Mailing list pgsql-performance

From John Smith
Subject Re: Performance of aggregates over set-returning functions
Date
Msg-id b88f0d670801081933t6c7cc50ci896a94d7d9f7ec17@mail.gmail.com
Whole thread Raw
In response to Re: Performance of aggregates over set-returning functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Performance of aggregates over set-returning functions
List pgsql-performance
> > Interestingly though, when the range in the generate_series() was
> > small enough to fit in 4 bytes of memory (e.g.
> > generate_series(1,1000000000) ), the above query completed consuming
> > only negligible amount of memory. So, it looked like the aggregate
> > computation was being pipelined with the tuples returned from
> > generate_series().
>
> It's pipelined either way.  But int8 is a pass-by-reference data type,
> and it sounds like we have a memory leak for this case.

Thanks for your reply. How easy is it to fix this? Which portion of
the code should we look to change?

- John

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Performance of aggregates over set-returning functions
Next
From: Tom Lane
Date:
Subject: Re: Performance of aggregates over set-returning functions