Re: BUG #15114: logical decoding Segmentation fault - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #15114: logical decoding Segmentation fault
Date
Msg-id 20180315145627.k735cejk3zejuimi@alvherre.pgsql
Whole thread Raw
In response to BUG #15114: logical decoding Segmentation fault  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15114: logical decoding Segmentation fault  (Петър Славов <pet.slavov@gmail.com>)
List pgsql-bugs
PG Bug reporting form wrote:

> --- Code dump: ---
> ------------------
> Reading symbols from /usr/lib/postgresql/10/bin/postgres...Reading symbols
> from
> /usr/lib/debug/.build-id/a3/2aff963eb198ec48d1946523ef49379fa49c5e.debug...done.
> done.
> [New LWP 26112]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by 'postgres: 10/main: wal sender process lg_replica
> ip-10-4-1-11.eu-west-1.compute'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  GetActiveSnapshot () at
> /build/postgresql-10-drhiey/postgresql-10-10.3/build/../src/backend/utils/time/snapmgr.c:843
> 843    /build/postgresql-10-drhiey/postgresql-10-10.3/build/../src/backend/utils/time/snapmgr.c:
> No such file or directory.
> (gdb)

Can you do a "bt" in that gdb and paste the output, please?



-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15114: logical decoding Segmentation fault
Next
From: Fabio Pardi
Date:
Subject: Re: Postgres 10.3 delete on partition table cannot execute, out ofmemory.