Re: DBT-3 with SF=20 got failed - Mailing list pgsql-hackers

From Kohei KaiGai
Subject Re: DBT-3 with SF=20 got failed
Date
Msg-id CADyhKSU3Sh37Hh8dgqCuv6tU2J-A17trgOeRBbK6TyjpUB6CMA@mail.gmail.com
Whole thread Raw
In response to Re: DBT-3 with SF=20 got failed  (Jan Wieck <jan@wi3ck.info>)
List pgsql-hackers
2015-06-11 23:20 GMT+09:00 Jan Wieck <jan@wi3ck.info>:
> On 06/11/2015 09:53 AM, Kouhei Kaigai wrote:
>>>
>>> curious: what was work_mem set to?
>>>
>> work_mem=48GB
>>
>> My machine mounts 256GB physical RAM.
>
>
> work_mem can be allocated several times per backend. Nodes like sort and
> hash_aggregate may each allocate that much. You should set work_mem to a
> fraction of physical-RAM / concurrent-connections depending on the
> complexity of your queries. 48GB does not sound reasonable.
>
Smaller number of max_connections and large work_mem configuration are
usual for typical OLAP workloads.

Even if configuration is not reasonable, it is not a right error message.
People cannot understand how to fix it.

psql:query21.sql:50: ERROR:  invalid memory alloc request size 1073741824



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: DBT-3 with SF=20 got failed
Next
From: Robert Haas
Date:
Subject: Re: Entities created in one query not available in another in extended protocol