base dir

[pr1mo]

if i have some old db's that are taking up for example 100GB each. i hardly ever use them but i want to still access them possibly in the future. if my hd is running out of space and i want to put more db's into it still can I move out the files inside the numbered db folder inside postgres\data\base onto a dif drive and when i want to access db then i move back into the dir and load up pt db?

so basically question is if i move files out and then at a later date move them back in do i damage db at all?

[kraada]

Moving files manually out of your PostgreSQL base directory will not work well. The best thing to do is to upgrade to Beta 29.1 and use the Backup function there. Backup the database you want to get rid of, then delete it. You can zip up the backup file as that will save a lot of space (it should shrink by 90%+), and then restore the file later if you so desire.

[pr1mo]

ran a backup with 29.1 and tried saving file on 2 dif hard drives. one had 260gigs free and other had 560gigs free and the db was definitely not bigger than that. got an error both times saying: pg_dump: [tar archiver] archive member too large for tar format

[pr1mo]

just tried a lot smaller db and got same thing too

[WhiteRider]

PT3's built-in backup doesn't compress the backups (although it may use tar internally I guess).
Please enable logging, restart PT3 and run the backup again and report your problem so that we can investigate.
The backup process is being re-worked for the next release, though, to make things easier so it will hopefully avoid any of these kind of issues.
You could backup your databases with PGAdmin instead - click here for directions.

[pr1mo]

tried it again after a restart and got same pop up. created ticket. ticket_id=75688

[WhiteRider]

Thanks - we'll get back to you via your ticket.