Обсуждение: BUG #15131: "ERROR: function pg_current_xlog_location() does notexist" in PGAdmin III

The following bug has been logged on the website:

Bug reference:      15131
Logged by:          Thomas Kinney
Email address:      tkinney.usmc@gmail.com
PostgreSQL version: 10.3
Operating system:   Centos 7 Server
Description:

Upgrade from 9.6.8 to 10.3 and used the 10.3 version of pg_dumpall.
Everything went smoothly, no errors.  Launched PGAdmin III and when I open
my database I get the following error:

ERROR: function pg_current_xlog_location() does not exist.

I can clear the error messages and the database seems to function
normally.

If a patch exists, I cannot find it.

On 28 March 2018 at 12:42, PG Bug reporting form <noreply@postgresql.org> wrote:
> ERROR: function pg_current_xlog_location() does not exist.

This was renamed to pg_current_wal_lsn() in pg10.


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

=?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.org> writes:
> Upgrade from 9.6.8 to 10.3 and used the 10.3 version of pg_dumpall. 
> Everything went smoothly, no errors.  Launched PGAdmin III and when I open
> my database I get the following error:

> ERROR: function pg_current_xlog_location() does not exist.

That function's been renamed to pg_current_wal_lsn(), as part of
an effort to standardize our terminology about WAL.

> If a patch exists, I cannot find it.

What you need is a newer PGAdmin version.  I'm not sure if III will
ever be updated to PG 10; you may need to get IV.

            regards, tom lane