![]() ![]() ![]() A pg_dumpall backup doesn't alot you that convenience, but does alot you the advantage of being able to restore your whole PgServer. the pg_dumpall (well its good to have a pg_dumpall version too), you can restore portions of a database from the backupįile. With a compressed backup of the database vs. pg_dump -i -h localhost -p 5432 -U postgres - F c -b -v -f "\somepath\postgres.backup" postgres.pg_dump -i -h localhost -p 5432 -U postgres - F c -b -v -f "\somepath\somedb.backup" somedb.In addition to the full dump or instead of the full dump if you are short on space or patience, you may want to selectively dump out important databases with a This is a fairly painless upgrade that just requires you to backup your data as a precautionary measure, but doesn't require a dump reload. If you are running version 8.3.1 and above then Now that 8.3.3 has come out, many of you should be considering upgrading if you haven't already since there are a couple of bug fixes as outlined inĪnd for those running 8.3.0 you will need to reindex your tables after as noted in. The blog comments are definitely worth a read. We also received numerous useful feedback from others on issues they We covered using the new PostgreSQL Yum repository to install the PostgreSQL 8.3.1 release on Fedora, RedHat Enterprise, and CentOS. In our April Issue An Almost Idiot's Guide to PostgreSQL YUM UPDATE we have new instructions for PostgreSQL 9.0 - refer to Installing PostgreSQL 9.0 via Yum
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |