On Thu, 9 Jun 2005, Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Yeah it is an ordering problem with pg_dump...
If you are using pg_restore you can hack around the problem by using
pg_restore's load-order-control switch (which was invented exactly to
let people work around pg_dump's problems ;-)). In this case though,
the simplest answer is probably to install tsearch2 into the new
database before you run pg_restore. It'll complain that the functions
already exist, but you can ignore that.
More then just that ... it errors out trying to create tables that already
exist from loading tsearch2.sql:
pg_restore: [archiver (db)] could not execute query: ERROR: relation
"pg_ts_dict" already exists
So that doesn't appear to be an option either ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
