From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Saurabh Gupta A <saurabh(dot)a(dot)gupta(at)ericsson(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Regarding "Point-in-time Recovery" feature |
Date: | 2015-02-27 08:55:48 |
Message-ID: | 54F03114.4000000@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/23/15 5:39 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?
Other than the overhead of the copy itself, it generally doesn't. There
are a very limited number of shortcuts we can take when wal_level is set
to minimal, such as not WAL logging the full contents of data inserted
into a table that was created/truncated in the same transaction, but
generally archiving doesn't impact performance (assuming you keep it
running correctly so pg_xlog doesn't fill up ;)
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2015-02-27 08:59:04 | Re: express composite type literal as text |
Previous Message | Thomas Kellerer | 2015-02-27 08:53:38 | Re: how to do merge in postgres ("with upsert as" not supported) |