So then the best way to do this kind of backup\restore is to use pg_dump? Is there any plan in the future to be able to do some sort of file-level backup like SqlServer?
-LK -----Original Message----- From: Richard Huxton [mailto:[EMAIL PROTECTED] Sent: Friday, May 18, 2007 10:35 AM To: Lee Keel Cc: Michael Nolan; Ron Johnson; pgsql-general@postgresql.org Subject: Re: [GENERAL] Large Database Restore Lee Keel wrote: > Thanks to everyone for their input on this. After reading all the emails > and some of the documentation (section 23.3), I think this is all a little > more than what I need. My database is basically read-only and all I was > looking to do is to be able to take snap-shots of it and be able to restore > on a developer's machine and not take 30 hours. So I was thinking I would > zip the data directories associated to my database, then the developer could > just copy the zip file and unzip in their own data directory. My question > now is: what file would a developer need to change to add this new directory > to their database list, or will it just automatically show up when they > refresh the service? You can't do a file-level backup of one database I'm afraid, only all databases in one installation. -- Richard Huxton Archonet Ltd This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
