Well this reproduces with pg_basebackup
Disturbing. I wonder what else if lurking around
> On Aug 2, 2017, at 10:34 PM, armand pirvu wrote:
>
> Hi
>
> Setting up the hot_standby the only way I could it get the base remote
> cluster running was including pg_xlog
> Now using rsync as opposed
Hi
Setting up the hot_standby the only way I could it get the base remote cluster
running was including pg_xlog
Now using rsync as opposed to pg_basebackup seems ok aka
psql postgres -c "select pg_start_backup('backup')"
rsync -a /var/lib/pgsql/9.5/data postgres@192.168.5.252:/var/lib/pgsql/9.
On Thu, Dec 19, 2013 at 11:56 PM, bricklen wrote:
>
> On Thu, Dec 19, 2013 at 1:27 AM, wd wrote:
>
>>
>> On Thu, Dec 19, 2013 at 2:24 PM, Amit Langote wrote:
>>
>>> "unexpected pageaddr" log entry in this case means the standby reached
>>> the end of existing WAL.
>>> So, just before connecting
On Thu, Dec 19, 2013 at 1:27 AM, wd wrote:
>
> On Thu, Dec 19, 2013 at 2:24 PM, Amit Langote wrote:
>
>> "unexpected pageaddr" log entry in this case means the standby reached
>> the end of existing WAL.
>> So, just before connecting to walsender for streaming replication, it
>> logs this.
>>
>
>
On Thu, Dec 19, 2013 at 2:24 PM, Amit Langote wrote:
> "unexpected pageaddr" log entry in this case means the standby reached
> the end of existing WAL.
> So, just before connecting to walsender for streaming replication, it logs
> this.
>
Thanks for your reply. So this means I can safely omit t
On Thu, Dec 19, 2013 at 12:25 PM, wd wrote:
>
> hi,
>
> We have upgrade our database from PostgreSQL 9.2.4 to 9.3.2, use dump &
> restore in a fresh db created by initdb.
>
> Then use pg_basebackup created 2 slave db, the error occur when start the
> database.
>
> db1
>
> [2013-12-19 04:00:5
hi,
We have upgrade our database from PostgreSQL 9.2.4 to 9.3.2, use dump &
restore in a fresh db created by initdb.
Then use pg_basebackup created 2 slave db, the error occur when start the
database.
db1
[2013-12-19 04:00:56.882 CST 17956 52b1fef8.4624 1 0]LOG:
database system was interrup
On 08/27/2012 05:17 AM, Viacheslav N Tararin wrote:
Good day.
I have got next log file after restart a standby server. The master
server all of the time was up and properly works.
It the message "unexpected pageaddr" and non exists log files indicates
about standby databases corrupted.
LOG: dat
Good day.
I have got next log file after restart a standby server. The master
server all of the time was up and properly works.
It the message "unexpected pageaddr" and non exists log files indicates
about standby databases corrupted.
LOG: database system was interrupted while in recovery at
--- On Tue, 1/12/09, Tom Lane wrote:
> > I'm doing my usual pull-the-plug tests on some new
> servers, and I'm
> > seeing this in the logs during redo. Is this in any
> way normal?
>
> Quite, this is one of the expected ways to detect
> end-of-WAL.
>
>
Excellent, thanks Tom.
--
Sent via
Glyn Astill writes:
> I'm doing my usual pull-the-plug tests on some new servers, and I'm
> seeing this in the logs during redo. Is this in any way normal?
Quite, this is one of the expected ways to detect end-of-WAL.
regards, tom lane
--
Sent via pgsql-general mailing
Hi Chaps,
I'm doing my usual pull-the-plug tests on some new servers, and I'm seeing this
in the logs during redo. Is this in any way normal? I'm guessing it is because
it's just under "LOG" rather than something like "WARNING", but I'm not taking
any chances.
I've got disk caches off, fsync o
12 matches
Mail list logo
