confusion

[thetruest]

its not a new machine. i just want it off the c drive. I have a small partition and i didn't know the db data was stored where postgre is (c drive)

[thetruest]

When you have the new database restored on the new machine, fire up PT3 on the machine and see that everything is working. The only reason I say to uninstall PostgreSQL last is because that way in case something goes wrong you won't have damaged your data.

As I'm not a CardRunners member, I can't comment on your linked thread . . .

i also don't have pt3. I have no space left on c drive. I want the databases that are taking up all the space on a different partition.


i have no idea why it pasted a cardrunner link. Sorry, the real link is http://www.pokertracker.com/forums/view ... f=17&t=526

[kraada]

Because there are two options:

Actually move the entire database over which is what I previously recommended (mostly because it's easier), or move just the data from the database but keep PostgreSQL installed on your primary drive which is what _dave_is suggesting. It will give a performance boost but obviously the process is a bit more involved. Both will work.

[thetruest]

Because there are two options:

Actually move the entire database over which is what I previously recommended (mostly because it's easier), or move just the data from the database but keep PostgreSQL installed on your primary drive which is what _dave_is suggesting. It will give a performance boost but obviously the process is a bit more involved. Both will work.

ok I'm assuming you mean what dave is suggesting will give a performance boost, as well as move the data in the postgre folder off my c drive and free up the space. Why would that give a performance boost over just moving all of postgre to another drive?


i was not sure if what dave was suggesting would move the data off the original drive to whatever other drive you want it to go... but if it does that and frees up the gigs of space i need as well as give a performance boost over just manually moving postgre altogether via reinstalling then i'll opt for that. But i seriously can't understand which gives what 'perofrmance boost' from what you are saying.

Also, in that link dave was talkin about PT3 not pt2. I know this is a pt3 forum but i also can't find anything about pt2 in the faqs and i originally started this as a postgre for pt3 thread.

[kraada]

I don't know nearly as much about PTv2 if you want help with that you're best off creating a thread on the PTv2 forum and Pat will help.

The reason you get a performance boost using a tablespace is that the postgres log files are then still written on your primary hard drive. These also only give boosts if you're talking about two physically separate drives. If it's one drive that's partitioned there's no benefit. The way PostgreSQL works it's constantly keeping a log of what happens to the database before committing any changes, so if those logs are elsewhere from the database the hard drives in question can work faster as each can do one dedicated part of the job.

[thetruest]

I don't know nearly as much about PTv2 if you want help with that you're best off creating a thread on the PTv2 forum and Pat will help.

The reason you get a performance boost using a tablespace is that the postgres log files are then still written on your primary hard drive. These also only give boosts if you're talking about two physically separate drives. If it's one drive that's partitioned there's no benefit. The way PostgreSQL works it's constantly keeping a log of what happens to the database before committing any changes, so if those logs are elsewhere from the database the hard drives in question can work faster as each can do one dedicated part of the job.

No offense but something seriously bugs me about the answers in this thread. I've moved around in circles while half of what you suggested either didn't apply or didn't work. I can't just reinstall Postgre and then delete the old dir. Running an updated versions installer only brings up the old install and i have to delete that first.

I originally asked if i could just copy paste postgre (which obviously doesn't work now that i see). But somehow you figured i was talking about seperate machines?

Anyway, i'm tired of wasting time so if the database is fucked oh well, i am just going to delete and reinstall without knowing about the longevity of the db, even backups.

[WhiteRider]

There was only one brief reply by kraada mentioning a separate machine, and actually it doesn't make any difference in that context - to move a database you need to backup and restore it, whether to a new drive or new machine. You will also need to do this if you want to upgrade to a newer version.
There is a description of how to do that in the Database / Postgres FAQ.
There is also a guide on re-installing postgres which you may find useful: How to reinstall Postgres.

If you are still having trouble, please explain clearly exactly what it is you want to do, and what problems you have doing it.