pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedcould not find function "LWGEOM_distance_ellipsoid_point"
4+ messages / 3 participants
[nested] [flat]
* could not find function "LWGEOM_distance_ellipsoid_point"
@ 2012-07-16 04:57 Stephen Davies <sdavies@sdc.com.au>
2012-07-16 05:47 ` Re: could not find function "LWGEOM_distance_ellipsoid_point" Tom Lane <tgl@sss.pgh.pa.us>
2012-07-26 18:30 ` Re: could not find function "LWGEOM_distance_ellipsoid_point" Bruce Momjian <bruce@momjian.us>
0 siblings, 2 replies; 4+ messages in thread
From: Stephen Davies @ 2012-07-16 04:57 UTC (permalink / raw)
To: pgsql-admin
Greetings.
I am trying to upgrade a PostgreSQL/PostGIS database from 8.4.0 to 0.1.4 using
pg_upgrade.
The "active check" run of pg_upgrade was successful but when I try the real
thing, I get:
-bash-4.1$ /usr/local/pgsql/bin/pg_upgrade -b /usr/bin -B /usr/local/pgsql/bin
-d /data1/copy/data -D /data1/pgsql914/data -k -l /tmp/pg_log
Performing Consistency Checks
-----------------------------
Checking current, bin, and data directories ok
Checking cluster versions ok
Checking database user is a superuser ok
Checking for prepared transactions ok
Checking for reg* system oid user data types ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for large objects ok
Creating catalog dump ok
Checking for prepared transactions ok
Checking for presence of required libraries ok
| If pg_upgrade fails after this point, you must
| re-initdb the new cluster before continuing.
| You will also need to remove the ".old" suffix
| from /data1/copy/data/global/pg_control.old.
Performing Upgrade
------------------
Adding ".old" suffix to old global/pg_control ok
Analyzing all rows in the new cluster ok
Freezing all rows on the new cluster ok
Deleting new commit clogs ok
Copying old commit clogs to new server ok
Setting next transaction id for new cluster ok
Resetting WAL archives ok
Setting frozenxid counters in new cluster ok
Creating databases in the new cluster ok
Adding support functions to new cluster ok
Restoring database schema to new cluster
psql:/data1/pgsql840/pg_upgrade_dump_db.sql:52010: ERROR: could not find
function "LWGEOM_distance_ellipsoid_point" in file "/usr/lib/liblwgeom.so"
There were problems executing "/usr/local/pgsql/bin/psql" --set
ON_ERROR_STOP=on --no-psqlrc --port 5432 --username "postgres" -f
"/data1/pgsql840/pg_upgrade_dump_db.sql" --dbname template1 >> "/tmp/pg_log"
Failure, exiting
Lines 52004 to 52010 in pg_upgrade_dump_db.sql are:
--
-- Name: distance_spheroid(geometry, geometry, spheroid); Type: FUNCTION;
Schema: public; Owner: postgres
--
CREATE FUNCTION distance_spheroid(geometry, geometry, spheroid) RETURNS double
precision
LANGUAGE c IMMUTABLE STRICT
AS '/usr/lib/liblwgeom', 'LWGEOM_distance_ellipsoid_point';
(I used the rsync method suggested in the last paragraph of the pg_upgrade man
pages to create a copy of the databases to be upgraded.
This works fine except that the paragraph should also point out that the file
postmaster.pid must be deleted from the copy to avoid an error message from
pg_upgrade.)
--
=============================================================================
Stephen Davies Consulting P/L Phone: 08-8177 1595
Adelaide, South Australia. Mobile:040 304 0583
Records & Collections Management.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: could not find function "LWGEOM_distance_ellipsoid_point"
2012-07-16 04:57 could not find function "LWGEOM_distance_ellipsoid_point" Stephen Davies <sdavies@sdc.com.au>
@ 2012-07-16 05:47 ` Tom Lane <tgl@sss.pgh.pa.us>
2012-07-16 06:05 ` Re: could not find function "LWGEOM_distance_ellipsoid_point" Stephen Davies <sdavies@sdc.com.au>
1 sibling, 1 reply; 4+ messages in thread
From: Tom Lane @ 2012-07-16 05:47 UTC (permalink / raw)
To: Stephen Davies <sdavies@sdc.com.au>; +Cc: pgsql-admin
Stephen Davies <sdavies@sdc.com.au> writes:
> psql:/data1/pgsql840/pg_upgrade_dump_db.sql:52010: ERROR: could not find
> function "LWGEOM_distance_ellipsoid_point" in file "/usr/lib/liblwgeom.so"
I think you'd have better luck asking about that on the postgis lists
--- from here it looks like a version-to-version incompatibility in
postgis.
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: could not find function "LWGEOM_distance_ellipsoid_point"
2012-07-16 04:57 could not find function "LWGEOM_distance_ellipsoid_point" Stephen Davies <sdavies@sdc.com.au>
2012-07-16 05:47 ` Re: could not find function "LWGEOM_distance_ellipsoid_point" Tom Lane <tgl@sss.pgh.pa.us>
@ 2012-07-16 06:05 ` Stephen Davies <sdavies@sdc.com.au>
0 siblings, 0 replies; 4+ messages in thread
From: Stephen Davies @ 2012-07-16 06:05 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin
I have done that but still think my last comment is relevant here too.
Cheers,
Stephen
On Monday, July 16, 2012 03:17:08 PM Tom Lane wrote:
> Stephen Davies <sdavies@sdc.com.au> writes:
> > psql:/data1/pgsql840/pg_upgrade_dump_db.sql:52010: ERROR: could not find
> > function "LWGEOM_distance_ellipsoid_point" in file
> > "/usr/lib/liblwgeom.so"
>
> I think you'd have better luck asking about that on the postgis lists
> --- from here it looks like a version-to-version incompatibility in
> postgis.
>
> regards, tom lane
--
=============================================================================
Stephen Davies Consulting P/L Phone: 08-8177 1595
Adelaide, South Australia. Mobile:040 304 0583
Records & Collections Management.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: could not find function "LWGEOM_distance_ellipsoid_point"
2012-07-16 04:57 could not find function "LWGEOM_distance_ellipsoid_point" Stephen Davies <sdavies@sdc.com.au>
@ 2012-07-26 18:30 ` Bruce Momjian <bruce@momjian.us>
1 sibling, 0 replies; 4+ messages in thread
From: Bruce Momjian @ 2012-07-26 18:30 UTC (permalink / raw)
To: Stephen Davies <sdavies@sdc.com.au>; +Cc: pgsql-admin
On Mon, Jul 16, 2012 at 02:27:45PM +0930, Stephen Davies wrote:
> (I used the rsync method suggested in the last paragraph of the pg_upgrade man
> pages to create a copy of the databases to be upgraded.
> This works fine except that the paragraph should also point out that the file
> postmaster.pid must be deleted from the copy to avoid an error message from
> pg_upgrade.)
OK, we already document the problems with postmaster.pid and rsync in
the backup section, so I added a mention of that to the pg_upgrade docs,
and backpatched that to 9.2.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Attachments:
rsync.diff (text/x-diff, 985B) download
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
new file mode 100644
index cffcebb..fcbe551
*** a/doc/src/sgml/pgupgrade.sgml
--- b/doc/src/sgml/pgupgrade.sgml
*************** psql --username postgres --file script.s
*** 530,536 ****
of the old cluster, use <command>rsync</> to create a dirty
copy of the old cluster while the server is running, then shut down
the old server and run <command>rsync</> again to update the copy with any
! changes to make it consistent.
</para>
<refsect2>
--- 530,538 ----
of the old cluster, use <command>rsync</> to create a dirty
copy of the old cluster while the server is running, then shut down
the old server and run <command>rsync</> again to update the copy with any
! changes to make it consistent. You might want to exclude some
! files, e.g. <filename>postmaster.pid</>, as documented in <xref
! linkend="backup-lowlevel-base-backup">.
</para>
<refsect2>
end of thread, other threads:[~2012-07-26 18:30 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2012-07-16 04:57 could not find function "LWGEOM_distance_ellipsoid_point" Stephen Davies <sdavies@sdc.com.au>
2012-07-16 05:47 ` Tom Lane <tgl@sss.pgh.pa.us>
2012-07-16 06:05 ` Stephen Davies <sdavies@sdc.com.au>
2012-07-26 18:30 ` Bruce Momjian <bruce@momjian.us>
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