Vladimir,
* Vladimir Borodin (r...@simply.name) wrote:
> > 20 янв. 2017 г., в 18:06, Stephen Frost написал(а):
> >
> > Right, without incremental or compressed backups, you'd have to have
> > room for 7 full copies of your database. Have you looked at what your
> > incrementals would be like wi
> 20 янв. 2017 г., в 18:06, Stephen Frost написал(а):
>
> Right, without incremental or compressed backups, you'd have to have
> room for 7 full copies of your database. Have you looked at what your
> incrementals would be like with file-level incrementals and compression?
Most of our DBs can’
Vladimir,
* Vladimir Borodin (r...@simply.name) wrote:
> > 20 янв. 2017 г., в 16:40, Stephen Frost написал(а):
> >> 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],
> 20 янв. 2017 г., в 16:40, Stephen Frost написал(а):
>
> Vladimir,
>
>> 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 d
Vladimir,
* Vladimir Borodin (r...@simply.name) wrote:
> > 20 янв. 2017 г., в 15:22, Stephen Frost написал(а):
> >> 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
> 20 янв. 2017 г., в 15:22, Stephen Frost написал(а):
>>
>> 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 lo
* Pavel Stehule (pavel.steh...@gmail.com) wrote:
> 2017-01-20 12:53 GMT+01:00 Dinesh Chandra 12108 :
> > 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.ht
2017-01-20 12:53 GMT+01:00 Dinesh Chandra 12108 :
> Dear Pavel,
>
>
>
> 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
Dear Pavel,
Thanks for quick response.
May I know how can I use physical full backup with export transaction segments.
Regards,
Dinesh Chandra
|Database administrator (Oracle/PostgreSQL)| Cyient Ltd. Noida.
--
Mobile: +91-9953975849
I hope you realise that 9.1 is EOLed - http://blog.2ndquadrant.com/
postgresql-9-1-end-of-life/
Which means that the version that you are using will not receive any
updates which includes critical updates to performance and security.
If I were you, I would work on the issues that stops me from up
Hi
2017-01-20 12:43 GMT+01:00 Dinesh Chandra 12108 :
> Exactly parallel option is there in version 9.3 but I can’t upgrade new
> version due to some concerns.
>
> Could you suggest in 9.1 how may I fix it.
>
1. don't use it - you can use physical full backup with export transaction
segments.
or
Exactly parallel option is there in version 9.3 but I can’t upgrade new version
due to some concerns.
Could you suggest in 9.1 how may I fix it.
Regards,
Dinesh Chandra
|Database administrator (Oracle/PostgreSQL)| Cyient Ltd. Noida.
If you can upgrade to a newer version, there is parallel pg dump.
Documentation -
https://www.postgresql.org/docs/current/static/backup-dump.html
Related blog -
http://paquier.xyz/postgresql-2/postgres-9-3-feature-highlight-parallel-pg_dump/
Which can give significant speed up depending on your
Hi Expert,
I have a database having size around 1350 GB, created in PostgreSQL-9.1 in
Linux platform.
I am using pg_dump to take backup which takes around 12 hours to complete.
Could you please suggest me how I can make my backup fast so that it complete
in less hours?
Thanks in advance.
Regar
14 matches
Mail list logo
