| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Dinesh Chandra 12108 <Dinesh(dot)Chandra(at)cyient(dot)com>, "Madusudanan(dot)B(dot)N" <b(dot)n(dot)madusudanan(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Backup taking long time !!! |
| Date: | 2017-01-20 12:22:24 |
| Message-ID: | 20170120122224.GF18360@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
* Pavel Stehule (pavel(dot)stehule(at)gmail(dot)com) wrote:
> 2017-01-20 12:53 GMT+01:00 Dinesh Chandra 12108 <Dinesh(dot)Chandra(at)cyient(dot)com>:
> > Thanks for quick response.
> >
> > May I know how can I use physical full backup with export transaction
> > segments.
> >
>
> https://www.postgresql.org/docs/9.1/static/continuous-archiving.html
>
> This process can be automatized by some applications like barman
> http://www.pgbarman.org/
Last I checked, barman is still single-threaded.
If the database is large enough that you need multi-process backup, I'd
suggest looking at pgbackrest- http://www.pgbackrest.org.
pgbackrest has parallel backup, incremental/differential/full backup
support, supports compression, CRC checking, and a whole ton of other
good stuff.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Borodin | 2017-01-20 12:57:57 | Re: Backup taking long time !!! |
| Previous Message | Pavel Stehule | 2017-01-20 11:55:43 | Re: Backup taking long time !!! |