Re: BUG #15041: dsa alloc_object null pointer

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: daniel(at)fdr(dot)io, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15041: dsa alloc_object null pointer
Date: 2018-01-31 20:17:39
Message-ID: CAEepm=2E63D_+q1i+VMsEaNZ15j=e1S-RGgwGbYcPsZ3prHcBQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Feb 1, 2018 at 9:04 AM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> The cause is running out of DSM slots, but not handing that
> case correctly. I think this implies that you're running queries with
> a lot of Gather [Merge] nodes in them? The number of DSM slots is 64 +
> 2 * max_connections, so one workaround is to crank up max_connections,
> and another is just to disable parallelism for that query.

Or alternatively it could be running out of workers due to the
max_parallel_workers, max_worker_processes limits, which on reflection
may be more likely (the other cases I ran into like this ran out of
DSM slots, because they had very high numbers of Gather nodes).
Either way, it's running out of some resource needed for parallel
query and falling back to non-parallel execution, but Bitmap Heap Scan
had failed to anticipate that possibility.

--
Thomas Munro
http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2018-01-31 21:25:44 Re: [BUGS] BUG #14898: pg_upgrade documentation is misleading
Previous Message Thomas Munro 2018-01-31 20:04:57 Re: BUG #15041: dsa alloc_object null pointer