Re: Segmentation fault when max_parallel degree is very High

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Segmentation fault when max_parallel degree is very High
Date: 2016-05-05 06:29:57
Message-ID: CAA4eK1K1JM04bY7Yt8qguZL_kDoa-fanYxE1bRP8-XcUSWRpzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 4, 2016 at 8:31 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Dilip Kumar <dilipbalaut(at)gmail(dot)com> writes:
> > When parallel degree is set to very high say 70000, there is a
segmentation
> > fault in parallel code,
> > and that is because type casting is missing in the code..
>
> I'd say the cause is not having a sane range limit on the GUC.
>

I think it might not be advisable to have this value more than the number
of CPU cores, so how about limiting it to 512 or 1024?

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2016-05-05 07:17:42 Re: Is pg_control file crashsafe?
Previous Message Thomas Munro 2016-05-05 06:22:57 Re: Is pg_control file crashsafe?