From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Victor Yegorov <viy(at)pirmabanka(dot)lv> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: DB archiving |
Date: | 2003-03-17 14:45:20 |
Message-ID: | 1047912320.23066.1281.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
This is exactly the way pg_dump works. Essentially when you pg_dump, you
get a "snapshot" of your database at the moment you start pg_dump. While
other transaction can be occuring during your dump, the dump wont see
them thanks to MVCC.
Robert Treat
On Mon, 2003-03-17 at 05:33, Victor Yegorov wrote:
> Hello.
>
> I was speaking with my colleague about PostgreSQL maintenance and he
> asked
> me a question which I wasn't able to answer.
>
> Is it possible to make a full DB backup (one database, say 'test')
> online
> and be sure, that after restoring it it'll contain ALL and ONLY data at
> the
> time of backuping routine start.
>
> I want to be sure, that nothing additional will get into dump after I'll
> start pg_dump.
>
> Is this possible? Or, may be, such behaviour is on by default (I
> didn't find anything concerning my problem in the docs about pg_dump).
>
> Thank you.
>
> --
>
> Victor Yegorov
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-03-17 14:59:27 | Re: LVM snapshots |
Previous Message | Matt Clark | 2003-03-17 14:41:16 | Re: LVM snapshots |