From: | William Dunn <dunnwjr(at)gmail(dot)com> |
---|---|
To: | "Sachin Srivastava *EXTERN*" <ssr(dot)teleatlas(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: |
Date: | 2015-05-18 00:57:12 |
Message-ID: | CAEva=V=ok1m9kRiFtaD8ww16Qrp0XDSL01gXGo5mwTdueKFxNQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello Sachin,
I hate to respond by suggesting an alternative but it may be good to try
using pg_basebackup (Doc:
http://www.postgresql.org/docs/9.1/static/app-pgbasebackup.html) to back-up
your database. It takes a copy of the file system files rather than
querying the data as an ordinary connection which is much faster. Straight
file system backup is fast too but it may be more difficult to restore the
database to a consistent state. At this point pg_dump is very good for
exporting specific tables or schemas or for loading data into another dbms
but it is slow and has a lot of overhead because of MVCC. pg_basebackup is
faster, but does require you take a backup of the entire cluster.
*Will J. Dunn*
*willjdunn.com <http://willjdunn.com>*
On Fri, May 15, 2015 at 8:09 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
wrote:
> Sachin Srivastava wrote:
> > How can I fast my daily pg_dump backup. Can I use parallel option(Which
> is introduced in Postgres 9.3)
> > with Postgres 9.1. There is any way I can use this is for 9.1 database.
>
> You cannot do that.
>
> Switch to file system backup, that is much faster.
>
> Yours,
> Laurenz Albe
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | ben.play | 2015-05-18 06:06:54 | My index doesn't write anymore but read |
Previous Message | William Dunn | 2015-05-18 00:46:19 | Re: SELECT .. WHERE id IN(..) |