On 01/29/2016 05:06 PM, jflem...@kispring.com wrote:
The jsonb_agg function seems to have significantly worse performance
than its json_agg counterpart:
=> explain analyze select pa.product_id, jsonb_agg(attributes) from
product_attributes2 pa group by pa.product_id;
QUERY PLAN
The jsonb_agg function seems to have significantly worse performance
than its json_agg counterpart:
=> explain analyze select pa.product_id, jsonb_agg(attributes) from
product_attributes2 pa group by pa.product_id;
QUERY PLAN
--
Hi
> I ran operf on both backends, and they look quite similar, except that the
> number of samples is different (this is "opreport -c" output):
>
> CPU: Intel Sandy Bridge microarchitecture, speed 2899.8 MHz (estimated)
> Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a uni
I have a query that runs *slower* if I increase work_mem.
The execution plans are identical in both cases, except that a temp file
is used when work_mem is smaller.
The relevant lines of EXPLAIN ANALYZE output are:
With work_mem='100MB':
-> Hash Join (cost=46738.74..285400.61 rows=292 width=8)
