Re: Assertion failure in pg_copy_logical_replication_slot()

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Assertion failure in pg_copy_logical_replication_slot()
Date: 2020-06-25 02:16:04
Message-ID: a0dcbd06-f345-61f4-a201-85fff7d840ac@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020/06/24 23:58, Alvaro Herrera wrote:
> 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.

Thanks! Pushed.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-06-25 02:50:39 Re: should libpq also require TLSv1.2 by default?
Previous Message Michael Paquier 2020-06-25 02:07:33 Re: [PATCH] COPY command's data format option allows only lowercase csv, text or binary