Re: cache lookup errors for missing replication origins
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2017-09-06T06:51:14Z
Lists: pgsql-hackers
Attachments
- replorigin-elogs.patch (application/octet-stream) patch
On Tue, Sep 5, 2017 at 12:59 PM, Michael Paquier <michael.paquier@gmail.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
Commits
-
Fix more user-visible elog() calls.
- 32022e3f55ea 9.5.10 landed
- 9d742e19da22 9.6.6 landed
- ce60c2a28253 10.1 landed
- c097b271e8a1 11.0 landed