pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: johann@winkreports.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16233: Yet another "logical replication worker" was terminated by signal 11: Segmentation fault
Date: Sun, 26 Jan 2020 11:28:18 -0500
Message-ID: <30599.1580056098@sss.pgh.pa.us> (raw)
In-Reply-To: <16233-d3f4c2bf4d76018e@postgresql.org>
References: <16233-d3f4c2bf4d76018e@postgresql.org>

PG Bug reporting form <noreply@postgresql.org> writes:
> I browsed around and noticed a few people having similar issues with logical
> replication.
> To my eyes it looks similar to the issue here:
> https://www.postgresql.org/message-id/flat/16129-a0c0f48e71741e5f%40postgresql.org
> which was fixed here:
> https://git.postgresql.org/gitweb/?p=postgresql.git&a=commit&h=a2aa224e

The stack trace does look the same, but do you have the same triggering
condition we identified (that is, fairly wide column values in the
subscriber table that are not getting replaced during a
logical-replication update? or possibly dropped columns in the
subscriber table?)

> When is 12.2 due out? Feb 13?

https://www.postgresql.org/developer/roadmap/

How quickly downstream packages appear isn't entirely under our
control, though.

> Are there any daily Ubuntu builds available
> anywhere so I can test the patch for my purposes, before I try to compile
> from scratch?

Couldn't say, but with most packaging systems it's relatively simple
to rebuild a given package with a custom patch or two added.  (If
memory serves, with Debian's system you don't even have to modify
any files, just add the patch into the relevant subdirectory.)
That's a skill worth acquiring if you deal with open source a lot.

FWIW, I do know that Christoph does test builds for Debian and Ubuntu
on a pretty regular basis, because he complains when things break ;-).
Whether he makes those builds widely available, though, I don't know.

			regards, tom lane





view thread (4+ messages)  latest in thread

Message-ID: <30599.1580056098@sss.pgh.pa.us>
Permalink:  ../30599.1580056098@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/30599.1580056098@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, johann@winkreports.com
  Subject: Re: BUG #16233: Yet another "logical replication worker" was terminated by signal 11: Segmentation fault
  In-Reply-To: <30599.1580056098@sss.pgh.pa.us>
  References: <16233-d3f4c2bf4d76018e@postgresql.org> <30599.1580056098@sss.pgh.pa.us>

* 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