Re: Assertion failure in pg_copy_logical_replication_slot() - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Assertion failure in pg_copy_logical_replication_slot()
Date
Msg-id 20200624145847.GA18281@alvherre.pgsql
Whole thread Raw
In response to Re: Assertion failure in pg_copy_logical_replication_slot()  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: Assertion failure in pg_copy_logical_replication_slot()  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
On 2020-Jun-24, Fujii Masao wrote:

> > I think the errcode is a bit bogus considering the new case.
> > IMO ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE is more appropriate.
> 
> Agreed. So I updated the patch so this errcode is used instead.
> Patch attached.

LGTM.

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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical ()at walsender.c:2762
Next
From: Alvaro Herrera
Date:
Subject: Re: pg_resetwal --next-transaction-id may cause database failed torestart.