Re: ERROR: too many dynamic shared memory segments

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Jakub Glapa <jakub(dot)glapa(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ERROR: too many dynamic shared memory segments
Date: 2018-02-02 20:56:56
Message-ID: 5929.1517605016@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Feb 2, 2018 at 3:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Do you mind if I change that Assert to a run-time test?

> Hrm, I guess I could have done something like
> shm_toc_lookup(pcxt->toc, PARALLEL_KEY_ERROR_QUEUE, (pcxt->nworkers ==
> 0)).

OK, that'd work too. I'll make it so.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2018-02-03 05:27:35 Re: Postgres Planner "Inconsistency"?
Previous Message Robert Haas 2018-02-02 20:19:49 Re: ERROR: too many dynamic shared memory segments

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-02-02 21:05:25 Re: [HACKERS] path toward faster partition pruning
Previous Message Dmitry Dolgov 2018-02-02 20:54:45 Re: [HACKERS] Bug in to_timestamp().