Re: BUG #14997: Get segmentation fault on select sum(bigint_field)

Setting max_parallel_workers to 0  doesn’t help..

eps=# select sum(sum) from ternopil.offices_documents where commit_date BETWEEN '2017-01-01' AND '2017-12-31’;
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.

              name               | setting
---------------------------------+---------
 max_parallel_workers            | 0
 max_parallel_workers_per_gather | 2

postgresql.log:

2018-01-03 21:50:05 EET LOG:  server process (PID 26702) was terminated by signal 11: Segmentation fault
2018-01-03 21:50:05 EET DETAIL:  Failed process was running: select sum(sum) from ternopil.offices_documents where
commit_dateBETWEEN '2017-01-01' AND '2017-12-31'; 
2018-01-03 21:50:05 EET LOG:  terminating any other active server processes
2018-01-03 21:50:05 EET WARNING:  terminating connection because of crash of another server process
2018-01-03 21:50:05 EET DETAIL:  The postmaster has commanded this server process to roll back the current transaction
andexit, because another server process exited abnormally and possibly corrupted shared memory. 
2018-01-03 21:50:05 EET HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2018-01-03 21:50:05 EET WARNING:  terminating connection because of crash of another server process
2018-01-03 21:50:05 EET DETAIL:  The postmaster has commanded this server process to roll back the current transaction
andexit, because another server process exited abnormally and possibly corrupted shared memory. 
2018-01-03 21:50:05 EET HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2018-01-03 21:50:05 EET FATAL:  the database system is in recovery mode
2018-01-03 21:50:05 EET LOG:  archiver process (PID 26675) exited with exit code 1
2018-01-03 21:50:05 EET LOG:  all server processes terminated; reinitializing
2018-01-03 21:50:05 EET LOG:  database system was interrupted; last known up at 2018-01-03 21:48:27 EET
2018-01-03 21:50:05 EET FATAL:  the database system is in recovery mode
2018-01-03 21:50:05 EET FATAL:  the database system is in recovery mode
2018-01-03 21:50:05 EET LOG:  database system was not properly shut down; automatic recovery in progress
2018-01-03 21:50:05 EET LOG:  redo starts at 6D/8E002220
2018-01-03 21:50:05 EET LOG:  invalid record length at 6D/8E004270: wanted 24, got 0
2018-01-03 21:50:05 EET LOG:  redo done at 6D/8E004238
2018-01-03 21:50:05 EET LOG:  database system is ready to accept connections



> 3 янв. 2018 г., в 21:29, Tom Lane <tgl@sss.pgh.pa.us> написал(а):
>
> sector119 <sector119@gmail.com> writes:
>> How can I disable parallel queries?
>
> set max_parallel_workers to zero
>
>             regards, tom lane