From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | alexey(at)serinbol(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Consistent pg_dump's |
Date: | 2001-03-31 04:56:26 |
Message-ID: | 21925.986014586@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alexey Rodriguez Yakushev <alexey(at)serinbol(dot)com> writes:
> Let me rephrase the question, i have a web-based application which uses
> postgres as its backend. It must be operating 24 hours 7 days. If i want to
> make a backup of the database using pg_dump, wouldn't it be possible that a
> transaction occurs in the middle of the backup, leaving the backup
> inconsistent?
No. pg_dump will produce a consistent snapshot that does not show the
effects of transactions that start (or complete) after the pg_dump
transaction starts. See the "multi-version concurrency control" chapter
of the User's Guide.
Postgres has its share of problems for 24x7 operation (read about VACUUM
if you haven't yet) ... but producing self-consistent backups is not
one of 'em.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-03-31 05:42:29 | Re: dynamic field names in a function. |
Previous Message | Eric G. Miller | 2001-03-31 03:29:56 | Re: dynamic field names in a function. |