Re: cache lookup errors for missing replication origins

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: cache lookup errors for missing replication origins
Date: 2017-09-06 06:51:14
Message-ID: CAB7nPqSsLQA2th_epggz8UKj8rFi2rrd9A5vjo12LF-GP0JOdg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 5, 2017 at 12:59 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> ERROR: 42704: replication slot "%s" does not exist

s/slot/origin/

> As far as I can see, replorigin_by_oid makes no use of its missing_ok
> = false in the backend code, so letting it untouched would have no
> impact. replorigin_by_name with missing_ok = false is only used with
> SQL-callable functions, so it could be changed without any impact
> elsewhere (without considering externally-maintained replication
> modules).

As long as I don't forget, attached is a patch added as well to the
next CF. replorigin_by_oid should have the same switch from elog to
ereport in my opinion. Additional regression tests are included.
--
Michael

Attachment Content-Type Size
replorigin-elogs.patch application/octet-stream 2.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuro Yamada 2017-09-06 06:58:26 Re: CLUSTER command progress monitor
Previous Message Fabien COELHO 2017-09-06 06:42:15 Re: [WIP] Zipfian distribution in pgbench