| From: | Kovacs Zoltan Sandor <tip(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_dump + function/table hierarchy |
| Date: | 2000-07-31 18:52:46 |
| Message-ID: | Pine.LNX.4.05.10007312049230.17860-100000@pc10.radnoti-szeged.sulinet.hu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> This is fixed in the next version as well as an experimental version for
> 7.0.2 found at:
>
> ftp://ftp.rhyme.com.au/pub/postgresql/pg_dump/blobs/
>
> The solution (as suggested by Tom Lane) was to sort the items by OID before
> dumping them. This is not a perfect solution, but it will cover 95% of cases.
I tried this new pg_dump. It worked for me very well. But, for a
database with 10000 rows it wasn't too fast dumping out (twice slower than
the original one) and restoring it was three times slower.
Thanks again, Zoltan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hstenger | 2000-07-31 18:53:33 | Managing Rollback |
| Previous Message | Ross J. Reedstrom | 2000-07-31 18:08:33 | Re: Now PostgreSQL recovers from errors within trns |