Re: BAKUP ISSUE

From: hubert depesz lubaczewski <depesz(at)gmail(dot)com>
To: Ramesh T <rameshparnanditech(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: BAKUP ISSUE
Date: 2014-07-09 11:29:44
Message-ID: CAKrjmhcfeAoEzHgmuJgYDuGy3WJ4ADp75Af_iPjPSf2tNT1Wig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jul 9, 2014 at 12:45 PM, Ramesh T <rameshparnanditech(at)gmail(dot)com>
wrote:

> HI,
> I have a problem when i take backup using pg_basebackup and
> pg_start_backup('base');
> following ,
>

What is the problem? You didn't write it. Just some outputs and config, but
you never mentioned what is the problem itself.

> archive_mode = on
> archive_command = 'copy "%p" "C:\\Program
> Files\\PostgreSQL\\9.3\\data\\pg_xlog\\%f"'
>

This archive_command looks bad.

Is c:\program files\postgresql\9.3\data\pg_xlog directory for xlog for THIS
postgresql?
If yes - why would you want to copy xlog back to its original location?
If no - while it might work, I don't think it's safe to copy xlogs directly
to pg_xlog directory of slave (assuming it's slave).

depesz

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Francisco Olarte 2014-07-09 11:47:44 Re: php password authentication failed for user ...
Previous Message Spiros Ioannou 2014-07-09 11:27:01 Re: Largely inconsistent query execution speed, involving psql_tmp