From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: keiko713@gmail.com
Subject: BUG #15112: Unable to run pg_upgrade with earthdistance extension
Date: Wed, 14 Mar 2018 23:12:26 +0000
Message-ID: <152106914669.1223.5104148605998271987@wrigleys.postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 15112
Logged by: Keiko Oda
Email address: keiko713@gmail.com
PostgreSQL version: 10.3
Operating system: Ubuntu
Description:
This is similar to the bug report from 2016
(https://www.postgresql.org/message-id/20161015001424.1413.93990@wrigleys.postgresql.org).
where earthdistance extension is assuming that it's executed with public
schema in search_path.
With 10.3 release, Postgres has tighten the search_path during pg_upgrade
only to pg_catalog. This is problematic as it's now impossible to run
pg_upgrade with earthdistance extension (it fails with create index with
ll_to_earth function).
Prior to this, we were at least able to workaround by adding public schema
in search_path with pg_upgrade.
As it's recommended in the release note, earthdistance should adjust these
functions to not assume anything about what search path they are invoked
under.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, keiko713@gmail.com
Subject: Re: BUG #15112: Unable to run pg_upgrade with earthdistance extension
In-Reply-To: <152106914669.1223.5104148605998271987@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox