Re: Hot Standby: too many KnownAssignedXids - Mailing list pgsql-hackers

From Joachim Wieland
Subject Re: Hot Standby: too many KnownAssignedXids
Date
Msg-id AANLkTikyUTTUTzvN5rqrme2mWZBPstV=P8tAmwR-y_jW@mail.gmail.com
Whole thread Raw
In response to Re: Hot Standby: too many KnownAssignedXids  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Hot Standby: too many KnownAssignedXids
List pgsql-hackers
On Tue, Nov 23, 2010 at 8:45 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> On 19.11.2010 23:46, Joachim Wieland wrote:
>>
>> FATAL:  too many KnownAssignedXids. head: 0, tail: 0, nxids: 9978,
>> pArray->maxKnownAssignedXids: 6890
>
> Hmm, that's a lot of entries in KnownAssignedXids.
>
> Can you recompile with WAL_DEBUG, and run the recovery again with
> wal_debug=on ? That will print all the replayed WAL records, which is a lot
> of data, but it might give a hint what's going on.

Sure, but this gives me only one more line:

[...]
LOG:  redo starts at 1F8/FC00E978
LOG:  REDO @ 1F8/FC00E978; LSN 1F8/FC00EE90: prev 1F8/FC00E930; xid
385669; len 21; bkpb1: Heap - insert: rel 1663/16384/18373; tid
3829898/23
FATAL:  too many KnownAssignedXids
CONTEXT:  xlog redo insert: rel 1663/16384/18373; tid 3829898/23
LOG:  startup process (PID 4587) exited with exit code 1
LOG:  terminating any other active server processes


Joachim


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Assertion failure on hot standby
Next
From: Josh Berkus
Date:
Subject: Re: Suggested "easy" TODO: pg_dump --from-list