Re: BUG #18483: Segmentation fault in tests modules
От | Alexander Lakhin |
---|---|
Тема | Re: BUG #18483: Segmentation fault in tests modules |
Дата | |
Msg-id | 439c9310-1d71-f2c6-b213-a9a2ea732ba9@gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #18483: Segmentation fault in tests modules (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: BUG #18483: Segmentation fault in tests modules
|
Список | pgsql-bugs |
Hello Michael and Tom, 08.06.2024 01:29, Michael Paquier wrote: > On Fri, Jun 07, 2024 at 04:32:56PM -0400, Tom Lane wrote: >> The test_predtest problem is mine, will fix it in a bit. > Thanks. May I ask you about the project policy regarding such test modules failures? Do you think all of these should be fixed or it's ok to have some server-crashing modules in the tree? I'm asking because I collected a number of such defects but didn't dare to report them yet. For example: echo "CREATE EXTENSION test_shm_mq; SELECT test_shm_mq_pipelined(64, '', 1, 0); " > src/test/modules/test_shm_mq/sql/test_shm_mq.sql make -s check -C src/test/modules/test_shm_mq/ leads to: 1087 Assert(handle->slot < max_worker_processes); (gdb) bt #0 GetBackgroundWorkerPid (handle=0x7f7f7f7f00000000, ...) at bgworker.c:1087 #1 0x000055cab243b2a6 in shm_mq_counterparty_gone (...) at shm_mq.c:1193 ... Best regards, Alexander
В списке pgsql-bugs по дате отправления: