Re: Segmentation fault when max_parallel degree is very High

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Segmentation fault when max_parallel degree is very High
Date: 2016-05-04 15:01:09
Message-ID: 6794.1462374069@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

> or corrupt some memory. Need to typecast
> *i * PARALLEL_TUPLE_QUEUE_SIZE --> (Size)i * **PARALLEL_TUPLE_QUEUE_SIZE *and
> this will fix

That might "fix" it on 64-bit machines, but not 32-bit.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2016-05-04 15:12:45 Re: atomic pin/unpin causing errors
Previous Message Teodor Sigaev 2016-05-04 15:00:24 Re: tsvector filter problem