From: Khusro Jaleel <mailing-lists@kerneljack.com>
To: pgsql-admin@postgresql.org
Subject: Re: Issues with log-shipping replication
Date: Sun, 18 Dec 2011 15:57:54 +0000
Message-ID: <4EEE0D82.5070303@kerneljack.com> (raw)
In-Reply-To: <4EEA9705.6090806@gmail.com>
References: <4EEA361B.2010306@kerneljack.com>
<4EEA9705.6090806@gmail.com>
On 16/12/2011 00:55, Rural Hunter wrote:
> well, is pgsql capable to parse shell variables in postgresql.conf?
> anway you should check your master log. If it can not archive the wal,
> there will be errors reported in it.
Hi there,
I have removed the various shell variables from the postgresql.conf
file, cleaned out the data dir and started again. I can not see any
errors in the postgresql log files in "data/pg_log". They simply report
that Postgres was started up successfully, that's all. There are a few
files created in "data/pg_xlog", some of which are copied over to the
slave, but it seems some of them are not for some strange reason,
perhaps an oddity with using "scp" for this procedure?
You are referring to the "master" log file, is this the same log file I
am referring to, or is that is some different location?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mailing-lists@kerneljack.com
Subject: Re: Issues with log-shipping replication
In-Reply-To: <4EEE0D82.5070303@kerneljack.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox