From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | tom(at)minnesota(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Trouble Restore With Large Objects |
Date: | 2002-12-21 20:00:39 |
Message-ID: | 1601.1040500839@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Thomas T. Thai" <tom(at)minnesota(dot)com> writes:
> $pg_restore -d phpads phpads.pgsql.tar
> pg_restore: [archiver (db)] could not execute query: ERROR: type txtidx
> already exists
> The trouble here is pg_dump should have just moved on with this type of
> error instead of stop. That's what it does with a normal text restore.
Yeah. I have been intending to change pg_restore to not quit on error,
but haven't gotten around to it. I'd suggest you see about doing that.
Another possible workaround is to do a schema-only restore into a text
file that you can load with psql (thereby ignoring this error) followed
by a data-only restore with pg_restore. I think that would work but
have never tried it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Ploski | 2002-12-21 20:22:44 | Re: Unicode database + JDBC driver performance |
Previous Message | Tom Lane | 2002-12-21 19:57:51 | Re: Unicode database + JDBC driver performance |