Skip site navigation (1) Skip section navigation (2)

Apologies if you don't consider this a bug and I've wasted your time.

From: Steve Ingram <ingram(at)samsixedd(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Apologies if you don't consider this a bug and I've wasted your time.
Date: 2004-08-27 06:00:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs


I have a postgresql database that I have added postgis capabilities to.

When I pg_dump out the database, it outputs all the tables, functions, types
as you'd expect, but it outputs table definitions that reference postgis
functions/types *before* the functions/types themselves.

This means that when I restore the database on a different machine,
the table definitions complain because they don't know about the
types that are referenced further down the file.

I checked to see if I could force the pg_dump to be in a particular order,
but that doesn't seem possible (or I'm just blind :) )

I'm guessing the info is just coming out in OID order?

Of course, it may be an impossible task to do anything about this
and in my case I do have workarounds (not to mention I can edit the
file :) ), but I thought I'd mention it anyway.

Wonderful database by the way!




pgsql-bugs by date

Next:From: PostgreSQL Bugs ListDate: 2004-08-27 09:59:55
Subject: BUG #1233: JDBC driver: moveToCurrentRow fails
Previous:From: S Murthy KambhampatyDate: 2004-08-26 21:58:50
Subject: initdb errors, postgresql-8.0-beta

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group