Thread: BUG #15807: pg_upgrade does not account for renaming of system catalog column names

BUG #15807: pg_upgrade does not account for renaming of system catalog column names

From
PG Bug reporting form
Date:
The following bug has been logged on the website:

Bug reference:      15807
Logged by:          Richard Yen
Email address:      richyen3@gmail.com
PostgreSQL version: 10.8
Operating system:   CentOS 6
Description:

example: pg_stat_replication.sent_location was renamed to
pg_stat_replication.sent_lsn in v10.  If a view in 9.6 refers to
pg_stat_replication.sent_location, pg_upgrade fails entirely because "column
pg_stat_replication.sent_location does not exist"


PG Bug reporting form <noreply@postgresql.org> writes:
> example: pg_stat_replication.sent_location was renamed to
> pg_stat_replication.sent_lsn in v10.

Yeah, that's a documented compatibility issue, per the v10 notes:

  * Rename WAL-related functions and views to use lsn instead of location
    (David Rowley)

> If a view in 9.6 refers to
> pg_stat_replication.sent_location, pg_upgrade fails entirely because "column
> pg_stat_replication.sent_location does not exist"

It is not pg_upgrade's job to fix such things.  Sorry.

            regards, tom lane



Ok, thanks for the clarification!

--Richard

On Wed, May 15, 2019 at 11:39 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
PG Bug reporting form <noreply@postgresql.org> writes:
> example: pg_stat_replication.sent_location was renamed to
> pg_stat_replication.sent_lsn in v10.

Yeah, that's a documented compatibility issue, per the v10 notes:

  * Rename WAL-related functions and views to use lsn instead of location
    (David Rowley)

> If a view in 9.6 refers to
> pg_stat_replication.sent_location, pg_upgrade fails entirely because "column
> pg_stat_replication.sent_location does not exist"

It is not pg_upgrade's job to fix such things.  Sorry.

                        regards, tom lane