From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | howardnews(at)selestial(dot)com |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Backup Method |
Date: | 2015-07-03 10:15:23 |
Message-ID: | CAECtzeW4tQ9kvjyfCZm+Svi8mGx063DZ+82TTBvDRfW20u9tcw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Le 3 juil. 2015 12:03 PM, "howardnews(at)selestial(dot)com" <
howardnews(at)selestial(dot)com> a écrit :
>
> Hi everyone,
>
> I am reaching the point with my database backups where the backups are
taking too long, and starting to interfere with running of the system
during the day. So I am looking for a bit of sage advice as to how to
proceed.
>
> For a typical server, I have a single database cluster with multiple
database that I backup nightly using sequential pg_dumps to NFS.
>
> So what I am looking for is a backup regime with less impact that will
run overnight but faster or less impact than the pg_dump.
>
> Would a file system backup be the better option in PITR format, or is
pg_dumpall more efficient than pg_dump?
>
pg_dumpall is not more efficient than pg_dump. As far as I can tell, you're
looking for PITR backups.
From | Date | Subject | |
---|---|---|---|
Next Message | howardnews@selestial.com | 2015-07-03 10:25:50 | Re: Backup Method |
Previous Message | Fabio Pardi | 2015-07-03 10:14:17 | max number of locks |