Re: Regarding "Point-in-time Recovery" feature

From: luis(dot)sa(at)htip(dot)com(dot)br
To: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Regarding "Point-in-time Recovery" feature
Date: 2015-02-23 16:11:09
Message-ID: 4996f29f2cc2742ac92cb92afd200caf@htip.com.br
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

And there is an app to this: Barman --> http://www.pgbarman.org/

On Mon, 23 Feb 2015 10:03:35 -0600, Mathis, Jason wrote:
> Full explanation starts
>
> here: http://www.postgresql.org/docs/9.3/static/continuous-archiving.html
> [1].
>
> While there are some considerations to take in it does not relate to
> performance. Generally most production systems run with archiving on.
> Take a minute to read through the documentation and let us know if
> you
> have any questions. Most questions about "backup and recovery" should
> be asked in the admin mailing list.
>
> Good Luck,
>
> jason
>
> On Mon, Feb 23, 2015 at 5:38 AM, Saurabh Gupta A wrote:
>
>> Hello,
>>
>> Has anybody used online backup feature of postgreSQL? In fact
>> precise postgreSQL term is called: "Point-in-time Recovery" (PITR)
>> This means enabling following additional options in config:
>> ---
>> archive_command = on
>> archive_command = 'cp %p /usr/local/pgsql/pgDataPITR/wals/%f' #
>> This is only example path
>> ---
>>
>>  
>>
>> If yes then may I know how it is used and how it impacts database
>> performance?
>>
>>  
>>
>>  
>>
>> Regards:
>>
>> Saurabh
>>
>>  
>>
>>  
>
>
>
> Links:
> ------
> [1]
> http://www.postgresql.org/docs/9.3/static/continuous-archiving.html
> [2] mailto:saurabh(dot)a(dot)gupta(at)ericsson(dot)com

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Sergey Shchukin 2015-02-24 13:42:06 Issue with a hanging apply process on the replica db after vacuum works on primary
Previous Message Mathis, Jason 2015-02-23 16:03:35 Re: Regarding "Point-in-time Recovery" feature