Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)
От | Robert Haas |
---|---|
Тема | Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation) |
Дата | |
Msg-id | CA+TgmoZq5+7f-4nJrGWmbJ1NBJ24Jmbg2AZV_=L1npqNHvbs-A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation) (Prabhat Sahu <prabhat.sahu@enterprisedb.com>) |
Ответы |
Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)
|
Список | pgsql-hackers |
On Wed, Mar 7, 2018 at 8:13 AM, Prabhat Sahu <prabhat.sahu@enterprisedb.com> wrote:
-- Hi all,While testing this feature I found a crash on PG head with parallel create index using pgbanch tables.-- GUCs under postgres.confmax_parallel_maintenance_workers = 16 max_parallel_workers = 16max_parallel_workers_per_gather = 8 maintenance_work_mem = 8GBmax_wal_size = 4GB./pgbench -i -s 500 -d postgrespostgres=# create index pgb_acc_idx3 on pgbench_accounts(aid, abalance,filler);WARNING: terminating connection because of crash of another server processDETAIL: 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.HINT: In a moment you should be able to reconnect to the database and repeat your command.server closed the connection unexpectedlyThis probably means the server terminated abnormallybefore or while processing the request.The connection to the server was lost. Attempting reset: Failed.!>
That makes it look like perhaps one of the worker backends crashed. Did you get a message in the logfile that might indicate the nature of the crash? Something with PANIC or TRAP, perhaps?
В списке pgsql-hackers по дате отправления: