Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ivkm1-0001qV-2u for pgsql-bugs@arkaria.postgresql.org; Sun, 26 Jan 2020 16:28:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ivkly-0000Hp-MS for pgsql-bugs@arkaria.postgresql.org; Sun, 26 Jan 2020 16:28:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ivkly-0000Hi-EK for pgsql-bugs@lists.postgresql.org; Sun, 26 Jan 2020 16:28:30 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ivklp-00046X-JK for pgsql-bugs@lists.postgresql.org; Sun, 26 Jan 2020 16:28:29 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 00QGSIPJ030600; Sun, 26 Jan 2020 11:28:18 -0500 From: Tom Lane 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 In-reply-to: <16233-d3f4c2bf4d76018e@postgresql.org> References: <16233-d3f4c2bf4d76018e@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Sun, 26 Jan 2020 06:46:00 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <30598.1580056098.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 26 Jan 2020 11:28:18 -0500 Message-ID: <30599.1580056098@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > I browsed around and noticed a few people having similar issues with log= ical > replication. > To my eyes it looks similar to the issue here: > https://www.postgresql.org/message-id/flat/16129-a0c0f48e71741e5f%40post= gresql.org > which was fixed here: > https://git.postgresql.org/gitweb/?p=3Dpostgresql.git&a=3Dcommit&h=3Da2a= a224e 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 compil= e > 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