From: | Lincoln Yeoh <lylyeoh(at)mecomb(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Dumping and reloading stuff in 6.5.3 |
Date: | 2000-05-11 07:32:27 |
Message-ID: | 3.0.5.32.20000511153227.008e17d0@pop.mecomb.po.my |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Hi,
What is the recommended way to reload a database in 6.5.3?
Right now I tried something like:
psql -f testfile -u test > /dev/null 2>&1
(then enter username and password, and wait)
(testfile is a dump of a 36MB database)
And I think it works, but while it is running it affects the performance of
other unrelated databases severely. Should this be happening? Top only
shows four or so backends running, but the webapps are like grinding down
to 20 seconds or more per page. Normally our webapps can do 12 hits/sec or
so, so such a drastic drop is surprising. This is on a PIII 500MHz 512MB,
SCSI 9GB HDD system.
Also when I did a 30MB psql level copy (\copy) into a test database and
table, somehow the performance of _other_ databases was bad until I did a
vacuum (which took ages). This was rather surprising.
I'll probably switch to 7.0 soon and see if the issue crops up. I hope
copies are much faster in 7.0. Should I turn off fsync when doing bulk
copies? I'm worried that if the backend crashes duing the copy, the other
databases may get corrupted.
Any comments?
Thanks,
Link.
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Welche | 2000-05-11 10:53:15 | Re: Patches list broken? |
Previous Message | Tom Lane | 2000-05-11 05:51:57 | Re: Patches list broken? |
From | Date | Subject | |
---|---|---|---|
Next Message | Vince Vielhaber | 2000-05-11 10:44:25 | message in logs |
Previous Message | SAKAIDA Masaaki | 2000-05-11 06:53:58 | FETCH help |