[ADMIN] too slow

Shashi Gireddy gireddy at GMAIL.COM
Tue Feb 8 23:57:30 PST 2005


Thanks for your help, I am improving.

I did vacuum analyze, but no use. I created the mysql-dump file again
this time with mysqldump command prompt insted of mysql-front, It
created a 1.4gig file(insted of 8gig) but i dont know how to use this
file with postgresql COPY command, can anybody help me.

Thanks in advance,
shashi.


On Tue, 8 Feb 2005 20:56:38 -0600, Robert Becker Cope
<robert at gonkgonk.com> wrote:
> gireddy at gmail.com wrote:
>
> > 8GB), It took 2days to import the whole thing into postgres. After all
> > the response from postgres is a disaster. It took 40sec's to run a
>
> Do you have indexes in place?
>
> Also, in my experience, after a dump and restore (or simply a restore, in
> your case) it is very importany to "vacuum analyze" the database. I
> usually do a "reindex" of the important tables before the vacuum, too.
> These steps can make a huge, huge difference.
>
> robert
>


--
Shashi Kiran Reddy. Gireddy,
Graduate Assistant,
CBER, University of Alabama.
http://www.cs.ua.edu/shashi
Home: 205-752-5137 Cell: 205-657-1438



More information about the MapServer-users mailing list