Re: Parallel bitmap heap scan

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Rafia Sabih <rafia(dot)sabih(at)enterprisedb(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel bitmap heap scan
Date: 2017-02-08 15:59:29
Message-ID: CA+TgmobNb94+KsWMoqShuc3MkmvLOvPmWU468Sej7WkNX0u0Yg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 8, 2017 at 8:58 AM, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> On Wed, Feb 8, 2017 at 7:01 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> You can store whatever you want in SH_TYPE's private_data member.
>> SH_ALLOCATE and SH_FREE both get a pointer to the SH_TYPE, so they
>> have access to that. Hmm, but there's no way to get that set in
>> SH_CREATE before SH_ALLOCATE is called. Maybe we need to add a
>> private_data argument to SH_CREATE. execGrouping.c could use that
>> instead of frobbing private_data directly:
>>
>> - hashtable->hashtab = tuplehash_create(tablecxt, nbuckets);
>> - hashtable->hashtab->private_data = hashtable;
>> + hashtable->hashtab = tuplehash_create(tablecxt, nbuckets, hashtable);
>
> Okay, will go ahead as you suggested. Patch attached for the same.

Looks good to me. If nobody has further ideas here, I'll push this
and your previous patch tomorrow.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-02-08 16:00:09 Re: chomp PQerrorMessage() in backend uses
Previous Message Robert Haas 2017-02-08 15:55:18 Re: pageinspect: Hash index support