From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: druidvav@gmail.com
Subject: BUG #16036: Segmentation fault while doing an update
Date: Fri, 04 Oct 2019 00:29:44 +0000
Message-ID: <16036-28184c90d952fb7f@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16036
Logged by: Антон Власов
Email address: druidvav@gmail.com
PostgreSQL version: 12.0
Operating system: PostgreSQL 12.0 (Debian 12.0-1.pgdg90+1) on x86_64
Description:
I am having segmentation fault like this:
2019-10-04 02:30:02 MSK [16919-6] LOG: server process (PID 18415) was
terminated by signal 11: Segmentation fault
2019-10-04 02:30:02 MSK [16919-7] DETAIL: Failed process was running:
update tracking.test_session set list_position = list_position + 1 where id
= $1
2019-10-04 02:30:02 MSK [16919-8] LOG: terminating any other active server
processes
When there are several queries running simultaneously. Tried to get some
info from coredump, but that's all i have:
(gdb) bt
#0 GetMemoryChunkContext (pointer=0x0) at
./build/../src/include/utils/memutils.h:127
#1 pfree (pointer=0x0) at ./build/../src/backend/utils/mmgr/mcxt.c:1033
Backtrace stopped: Cannot access memory at address 0x7ffc990e7218
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, druidvav@gmail.com
Subject: Re: BUG #16036: Segmentation fault while doing an update
In-Reply-To: <16036-28184c90d952fb7f@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox