Description
pg_dump is a utility for backing up a PostgreSQL database. It makes consistent backups even if the database is being used concurrently. pg_dump does not block other users accessing the database (readers or writers).
回答来自：
I have a 3GB database that is constantly modified and I need to make backups without stopping the server (Postgres 8.3).
My pg_dump runs for 5 minutes. What if the data is modified during the process? Do I get consistent backups? I don't want to find out when disaster strikes.
Postgres documentation doesn't say anything about this.
From the manual:
It makes consistent backups even if the database is being used concurrently.
So yes, you can trust the backup. Of course, it's PostgreSQL, you can trust your data in PostgreSQL.
pg_dump starts a transaction, similarly to how any other long running query will work. The consistency guarantees there come from the MVCC implementation. The dump will always be self-consistent within those rules.
All the fuzzy parts of MVCC are around around things like what order UPDATE transactions become visible to other clients and how the locks are acquired. pg_dump is strict about the ordering and acquires a read lock on the whole database to dump it. For most people, that's what they expect, and the mechanism used never causes any trouble. The main concurrency risk is that clients trying to change the database structure will be blocked while the dump is running. That doesn't impact the quality of the dump though.
阅读(862) | 评论(0) | 转发(0) |
