I used pgadmin to save and mine would not restore saying something about the encoding. I will have to be able to save and restore reliably as well.
Also I never heard anything further on the query running slow (I put up table defs and analyze with and without seq on). I am running into this on several of my views (I guess I am not too bright, because I still don’t get why it chooses seq scan on indexed tables). I can force it to use index and did see a little improvement, but the MSSQL was 3 secs and Postgres was like 9. Seeing as how I got the one viw to return faster (it was very complex view) on postgres, my guess is I still have stuff to do. I did try changing the cost to a lower number in config and redid my analyze, but it was still trying to do a seq scan.
Joel Fradkin
Wazagua, Inc.
[EMAIL PROTECTED]
-----Original Message-----
I'm attempting to restore a dump from one server to
another (one is a Mac and one is a Linux base, if that makes any difference). I
keep running into issues like this: |
- Re: [SQL] pg_restore problem Joel Fradkin
- Re: [SQL] pg_restore problem Tom Lane
- Re: [SQL] pg_restore problem Bradley Miller
- Re: [SQL] pg_restore problem Richard Huxton
- Re: [SQL] pg_restore problem Bradley Miller