Re: Logical Replication WIP

From: Petr Jelinek <petr(at)2ndquadrant(dot)com>
To: Erik Rijkers <er(at)xs4all(dot)nl>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Steve Singer <steve(at)ssinger(dot)info>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers-owner(at)postgresql(dot)org
Subject: Re: Logical Replication WIP
Date: 2016-11-27 18:57:06
Message-ID: 98343d79-f2e7-caa5-08bf-4ec18396c113@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22/11/16 18:42, Erik Rijkers wrote:
> On 2016-11-20 19:02, Petr Jelinek wrote:
>
>> 0001-Add-support-for-TE...cation-slots-v8.patch.gz (~8 KB)
>> 0002-Refactor-libpqwalreceiver-v8.patch.gz (~9 KB)
>> 0003-Add-PUBLICATION-catalogs-and-DDL-v8.patch.gz (~30 KB)
>> 0004-Add-SUBSCRIPTION-catalog-and-DDL-v8.patch.gz (~27 KB)
>> 0005-Define-logical-rep...output-plugi-v8.patch.gz (~13 KB)
>> 0006-Add-logical-replication-workers-v8.patch.gz (~43 KB)
>> 0007-Add-separate-synch...for-logical--v8.patch.gz (~2 KB)
>
> Apply, make, make check, install OK.
>
>
> A crash of the subscriber can be forced by running vacuum <published
> table> on the publisher.
>
>
> - publisher
> create table if not exists testt( id integer primary key, c text );
> create publication pub1 for table testt;
>
> - subscriber
> create table if not exists testt( id integer primary key, c text );
> create subscription sub1 connection 'dbname=testdb port=6444'
> publication pub1 with (disabled);
> alter subscription sub1 enable;
>
> - publisher
> vacuum testt;
>
> now data change on the published table, (perhaps also a select on the
> subscriber-side data) leads to:
>
>
> - subscriber log:
> TRAP: FailedAssertion("!(pointer != ((void *)0))", File: "mcxt.c", Line:
> 1001)
> 2016-11-22 18:13:13.983 CET 10177 LOG: worker process: ??)? (PID 10334)
> was terminated by signal 6: Aborted
> 2016-11-22 18:13:13.983 CET 10177 LOG: terminating any other active
> server processes
> 2016-11-22 18:13:13.983 CET 10338 WARNING: terminating connection
> because of crash of another server process
> 2016-11-22 18:13:13.983 CET 10338 DETAIL: The postmaster has commanded
> this server process to roll back the current transaction and exit,
> because another server process exited abnormally and possibly corrupted
> shared memory.
> [...]
>

Hi, thanks for report.

I very much doubt this is problem of vacuum as it does not send anything
to subscriber. Is there anything else you did on those servers?

--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Artur Zakirov 2016-11-27 18:59:43 Re: [BUG?] pg_event_trigger_ddl_commands() error with ALTER TEXT SEARCH CONFIGURATION
Previous Message Tom Lane 2016-11-27 18:45:47 Autovacuum breakage from a734fd5d1