From: | Mario Weilguni <mweilguni(at)sime(dot)com> |
---|---|
To: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | pg_restore and user defined types, several other pg_restore problems |
Date: | 2002-08-16 09:50:57 |
Message-ID: | 200208161150.57544.mweilguni@sime.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I'm using the ltree module and located several problems, I think not all problems are really ltree related but might be a pg_dump/pg_restore problem.
Here are the problems I've encountered:
* pg_restore tries to create a table with ltree and ltree[] datatypes before the type itself is created, so it fails.
* several functions are already defined in template1, so "create database " will restore these functions. pg_restore will try to restore those functions as well
and fails. Maybe "create or replace function" can be used here? I'm willing to do this if it's ok.
* I've gist indices on ltree[] columns, and when pg_restore tries to restore it it will report:
pg_restore: [archiver (db)] could not execute query: ERROR: data type ltree[] has no default operator class for access method "gist"
You must specify an operator class for the index or define a
default operator class for the data type
It seems those extra functions for index support are not restored. Removing the commit/end from ltree.sql and running it again (will report a lot of errors, but a few
inserts as well) will make this work again. However it requires a lot of DBA assistance to restore.
All other problems are solvable by using "pg_restore -L" and using a modified archiv index, but IMO this should work out of the box.
Best regards,
Mario Weilguni
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2002-08-16 10:58:45 | Re: pg_restore and user defined types, several other |
Previous Message | Teodor Sigaev | 2002-08-16 09:28:29 | Re: tsearch bug in 7.2.1? |