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

From: "Mathis, Jason" <jmathis(at)enova(dot)com>
To: Saurabh Gupta A <saurabh(dot)a(dot)gupta(at)ericsson(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Regarding "Point-in-time Recovery" feature
Date: 2015-02-23 16:03:35
Message-ID: CABAbqyeSB-CpmV4eLpGjvVSLY_witTnXONN4ysJev-5n7AgddA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Full explanation starts here:
http://www.postgresql.org/docs/9.3/static/continuous-archiving.html.

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 <
saurabh(dot)a(dot)gupta(at)ericsson(dot)com> 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
>
>
>
>
>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message luis.sa 2015-02-23 16:11:09 Re: Regarding "Point-in-time Recovery" feature
Previous Message Saurabh Gupta A 2015-02-23 11:38:42 Regarding "Point-in-time Recovery" feature