| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Thilo Hille" <thilo(at)resourcery(dot)de> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: pg_dump bug? |
| Date: | 2003-10-29 14:33:28 |
| Message-ID: | 3763.1067438008@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
"Thilo Hille" <thilo(at)resourcery(dot)de> writes:
> I am using postgresl 7.2.3. Yesterday i have dumped a database using pg_dump
> everthing was fine, but the dump was in the wrong order. There were indexes
> and views createded before the corresponding table was created.
There are some bugs along that line, particularly in older releases.
If you're using one of the archive output formats then pg_restore can
be used to alter the restore order into something that will work.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emmon Simbo | 2003-10-29 15:03:46 | Re: Viewing linked large postgres tables with Access: Running out of memory |
| Previous Message | Jim Beckstrom | 2003-10-29 13:50:50 | foxpro to postgresql 7.x |