Re: Segmentation fault when max_parallel degree is very High - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Segmentation fault when max_parallel degree is very High
Date
Msg-id CAA4eK1K1JM04bY7Yt8qguZL_kDoa-fanYxE1bRP8-XcUSWRpzw@mail.gmail.com
Whole thread Raw
In response to Re: Segmentation fault when max_parallel degree is very High  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, May 4, 2016 at 8:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Dilip Kumar <dilipbalaut@gmail.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

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Is pg_control file crashsafe?
Next
From: Amit Kapila
Date:
Subject: Re: Is pg_control file crashsafe?