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

From Robert Haas
Subject Re: DBT-3 with SF=20 got failed
Date
Msg-id CA+TgmoaKP2g6oTiYvpqc64Bhxt_7ncbeYR3fNmg7h-4sVQwxMA@mail.gmail.com
Whole thread Raw
In response to DBT-3 with SF=20 got failed  (Kouhei Kaigai <kaigai@ak.jp.nec.com>)
Responses Re: DBT-3 with SF=20 got failed  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
Re: DBT-3 with SF=20 got failed  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
On Wed, Jun 10, 2015 at 10:57 PM, Kouhei Kaigai <kaigai@ak.jp.nec.com> wrote:
> The attached patch replaces this palloc0() by MemoryContextAllocHuge() + memset().
> Indeed, this hash table is constructed towards the relation with nrows=119994544,
> so, it is not strange even if hash-slot itself is larger than 1GB.

You forgot to attach the patch, I think.  It looks to me like the size
of a HashJoinTuple is going to be 16 bytes, so 1GB/16 = ~64 million.
That's a lot of buckets, but maybe not unreasonably many if you've got
enough memory.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: DBT-3 with SF=20 got failed
Next
From: Kohei KaiGai
Date:
Subject: Re: DBT-3 with SF=20 got failed