| From: | Vladimir Borodin <root(at)simply(dot)name> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, 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:57:57 |
| Message-ID: | DE553F58-646E-49E8-94D1-31794C3E9040@simply.name |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> 20 янв. 2017 г., в 15:22, Stephen Frost <sfrost(at)snowman(dot)net> написал(а):
>>
>> 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.
Increments in pgbackrest are done on file level which is not really efficient. We have done parallelism, compression and page-level increments (9.3+) in barman fork [1], but unfortunately guys from 2ndquadrant-it don’t hurry to work on it.
And actually it would be much better to do a good backup and recovery manager part of the core postgres.
[1] https://github.com/secwall/barman
[2] https://github.com/2ndquadrant-it/barman/issues/21
--
May the force be with you…
https://simply.name
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-01-20 13:40:54 | Re: Backup taking long time !!! |
| Previous Message | Stephen Frost | 2017-01-20 12:22:24 | Re: Backup taking long time !!! |