Re: [HACKERS] Segmentation fault when max_parallel degree is very High

On Wed, May 4, 2016 at 11:01 AM, Tom Lane wrote: > Dilip Kumar writes: >> When parallel degree is set to very high say 7, there is a segmentation >> fault in parallel code, >> and that is because type casting is missing in the code.. > > I'd say the

Re: [HACKERS] Segmentation fault when max_parallel degree is very High

On Wed, May 4, 2016 at 8:31 PM, Tom Lane wrote: > > Dilip Kumar writes: > > When parallel degree is set to very high say 7, there is a segmentation > > fault in parallel code, > > and that is because type casting is missing in the code.. > > I'd say

Re: [HACKERS] Segmentation fault when max_parallel degree is very High

Dilip Kumar writes: > When parallel degree is set to very high say 7, 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. > or corrupt some memory.

[HACKERS] Segmentation fault when max_parallel degree is very High

When parallel degree is set to very high say 7, there is a segmentation fault in parallel code, and that is because type casting is missing in the code.. Take a look at below test code: create table abd(n int) with (parallel_degree=7); insert into abd values (generate_series(1,100));