| From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "Gary Chambers" <gwchamb(at)gmail(dot)com> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #3682: Incomplete database restore |
| Date: | 2007-10-20 08:09:01 |
| Message-ID: | 4719B79D.4030001@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Gary Chambers wrote:
> The following bug has been logged online:
>
> Bug reference: 3682
> Logged by: Gary Chambers
> Email address: gwchamb(at)gmail(dot)com
> PostgreSQL version: 8.3beta1
> Operating system: Mac OS X 10.4.10
> Description: Incomplete database restore
> Details:
>
> After dumping a database with pg_dump, then attempting to restore it, the
> restore fails with "invalid command \" error reports.
>
> Each individual database is dumped by:
> pg_dump --username=<owner> --file=<filename>
We're going to need more details. How did you attempt to restore it? Can
you post the dump file?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pedro Gimeno | 2007-10-20 09:37:07 | BUG #3684: After dump/restore, schema PUBLIC always exists |
| Previous Message | Tom Lane | 2007-10-20 03:05:24 | Re: PostgreSQL 8.2 Bug in casting varchar to int in SELECT ... WHERE IN ( ... ) |