Re: Parallel bitmap heap scan

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: Rafia Sabih <rafia(dot)sabih(at)enterprisedb(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(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>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel bitmap heap scan
Date: 2017-03-27 09:02:03
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

On Mon, Mar 27, 2017 at 12:53 PM, Rafia Sabih
<rafia(dot)sabih(at)enterprisedb(dot)com> wrote:
> Recently, on testing TPC-H 300 scale factor I stumbled on to a error
> for Q6, the test environment is as follows,
> work_mem = 1GB,
> shared_buffers = 10 GB,
> Effective_cache_size = 10GB
> random_page_cost = seq+page_cost =0.1
> The error message is, ERROR: invalid DSA memory alloc request size 1610612740
> In case required, stack trace is as follows,

Thanks for reporting. In pagetable_allocate, DSA_ALLOC_HUGE flag were
missing while allocating the memory from the DSA. I have also handled
the NULL pointer return from dsa_get_address.

Please verify with the attached patch.

Dilip Kumar

Attachment Content-Type Size
bitmap_hugepage_fix.patch application/octet-stream 1.0 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Kuntal Ghosh 2017-03-27 09:14:12 Re: exposing wait events for non-backends (was: Tracking wait event for latches)
Previous Message Pavan Deolasee 2017-03-27 08:49:03 Re: Patch: Write Amplification Reduction Method (WARM)