"Joshua D. Drake" <jd@commandprompt.com> 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.
regards, tom lane
