From: | luis(dot)roberto(at)siscobra(dot)com(dot)br |
---|---|
To: | pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Cc: | "alan(dot)formagi" <alan(dot)formagi(at)siscobra(dot)com(dot)br> |
Subject: | segfault with incremental sort |
Date: | 2020-10-30 17:54:17 |
Message-ID: | 622580997.37108180.1604080457319.JavaMail.zimbra@siscobra.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi!
I'm running a query that is causing the server to segfault.
This is the plan generated by setting "enable_incremental_sort" to off.
[ https://explain.depesz.com/s/T3sY | https://explain.depesz.com/s/T3sY ]
setting the option to "on", causes:
# 2020-10-30 14:49:06 -03 - - 519945 - - () : LOG:background worker "parallel worker" (PID 522547) was terminated by signal 11: Segmentation faul t
# 2020-10-30 14:49:06 -03 - ::1(46826) - 521801 - username- (database_name) : WARNING: terminating connection because of crash of another server process
# 2020-10-30 14:49:06 -03 - ::1(46826) - 521801 - username - (database_name) : DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
# 2020-10-30 14:49:06 -03 - ::1(46826) - 521801 - username - ( database_name ) : HINT: In a moment you should be able to reconnect to the database and repeat your command.
Running explain only gives the following plan:
[ https://explain.depesz.com/s/Eh3F | https://explain.depesz.com/s/Eh3F ]
Version:
PostgreSQL 13.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5), 64-bit
Installed via package manager.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-10-30 18:22:02 | Re: segfault with incremental sort |
Previous Message | Tom Lane | 2020-10-30 17:25:35 | Re: REL_13_STABLE Windows 10 Regression Failures |