PT3 performance tuning 2 HDDs

[WhiteRider]

If you are able to connect postgres to the old databases on the other drive then you won't need to re-import them - you could just backup/restore them.

After the update to Build 5 you will need to rerun full housekeeping on all your databases, yes.
Make sure you have plenty of free space on your hard disk before doing this - at least as much space as the size of your largest DB or clustering will take signifcantly longer. The speed of the housekeeping process has been improved in recent versions, though, so it shouldn't take as long as before.

[Beck]

If you are able to connect postgres to the old databases on the other drive then you won't need to re-import them - you could just backup/restore them.

After the update to Build 5 you will need to rerun full housekeeping on all your databases, yes.
Make sure you have plenty of free space on your hard disk before doing this - at least as much space as the size of your largest DB or clustering will take signifcantly longer. The speed of the housekeeping process has been improved in recent versions, though, so it shouldn't take as long as before.

OK, I was able to create a new database on my new HDD using the method outlined. Am I correct in assuming I have to do this every time I want to create a new database, to make sure it is created on my new harddive?

Regarding my old databases, I'm unsure of the backup/restore process.
I went in to pgAdmin III and is currently in the process of backing up a database. Do I have to create a new database on my new HDD, or is that done automatically upon restoring?

Considering I have to full housekeeping nomatter what due to the upgrade, and I have all the HH's still for all my databases, are there any differences from doing backup/restore than just reimporting everything?

[WhiteRider]

It depends how you have configured postgres - if it is configured to use the drive that you want then you won't need to do anything special, you can just create the databases through PT3.

The backup post in the Database / Postgres FAQ explains exactly what you need to do to restore a database using PGAdmin.

I expect that the backup/restore process would be a bit quicker, but my personal preference would be to create new databases and re-import the hands.
If it's a while since you imported the hands then you will benefit from this because some import bugs have been fixed, so some stats will be more accurate after a re-import anyway.

[Beck]

It depends how you have configured postgres - if it is configured to use the drive that you want then you won't need to do anything special, you can just create the databases through PT3.

Well, before new DB's were created on my old HDD. I followed the steps outlined in the second post in this thread, and was via the command prompt able to create a new DB on my new HDD. But I don't know if that is enough for future DB's created through PT3 to be put on the new HDD as well?

EDIT: I tried creating a new DB using PT3 and it was created on my old HDD. What do I need to do, to make my new HDD my default?

The backup post in the Database / Postgres FAQ explains exactly what you need to do to restore a database using PGAdmin.

I tried this, and it seemed to work, however, first I got a message upon restoring saying it had ignored 101 errors. I then hit OK, and it then continued. Then it appeared with a message about having ignored 115 errors. I hit OK again, the program worked a little bit and again informed of the 115 errors. This happened a couple more times untill I finally hit cancel.
I'm not sure if it just keeps trying to rerun the restore due to the errors? And what are the errors? it appears it had the same amount of hands a the old DB.

[WhiteRider]

What directions are you following - can you post the link please?
What errors did you get when you did the restore?

[live2bet]

Should i buy a faster HDD (http://www.newegg.com/Product/Product.a ... 6822136296) or a 7200RPM HDD would do?
My current OS is on a 7200RPM HDD.
Thanks.

[WhiteRider]

A faster hard drive will give you better performance, but a 7200 will work fine - it really depends how big your databases are [going to be]. If you can afford to get the faster drive I think you'll be glad you did.

[live2bet]

Thanks WhiteRider.
Let me know if i understand the whole thing...
OS on current 7200 drive and Database on new 10000 drive?

[WhiteRider]

Yes, that would be a pretty good setup.

[live2bet]

Thank you WhiteRider.
Ordering my HDD now.

Thanks again for such great support.