From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: M Rehman Kahloon <m.rehman@3gca.org>
Cc: pgsql-bugs@postgresql.org
Subject: Re: Segmentation Fault (Logical Replication)
Date: Thu, 30 Jan 2020 11:30:50 +0900
Message-ID: <20200130023050.GC1956@paquier.xyz> (raw)
In-Reply-To: <13037.1580311538@sss.pgh.pa.us>
References: <003801d5d69e$c77bbdd0$56733970$@3gca.org>
<13037.1580311538@sss.pgh.pa.us>
On Wed, Jan 29, 2020 at 10:25:38AM -0500, Tom Lane wrote:
> for some advice about what to put in a useful trouble report.
> Since you're getting crashes, we'd probably also wish to see
> a stack trace,
>
> https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
Impossible to say if that's Postgres problem without at least a
backtrace (even better a reproducible scenario), but you could also
consider contacting the maintainers of pglogical:
https://github.com/2ndQuadrant/pglogical
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: michael@paquier.xyz, tgl@sss.pgh.pa.us, m.rehman@3gca.org
Subject: Re: Segmentation Fault (Logical Replication)
In-Reply-To: <20200130023050.GC1956@paquier.xyz>
References: <003801d5d69e$c77bbdd0$56733970$@3gca.org> <13037.1580311538@sss.pgh.pa.us> <20200130023050.GC1956@paquier.xyz>
* 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