Re: XLogInsert scaling, revisited

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: XLogInsert scaling, revisited
Date: 2013-07-15 17:24:06
Message-ID: CAHGQGwGFuyR4LMrV=t=WCZc+t2Nra8OuB0KHDzJ_aC_6wGG1-Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 8, 2013 at 6:16 PM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> Ok, I've committed this patch now. Finally, phew!

I found that this patch causes the assertion failure. When I set up simple
replication environment and promoted the standby before executing any
transaction on the master, I got the following assertion failure.

2013-07-16 02:22:06 JST sby1 LOG: received promote request
2013-07-16 02:22:06 JST sby1 FATAL: terminating walreceiver process
due to administrator command
2013-07-16 02:22:06 JST sby1 LOG: redo done at 0/20000F0
2013-07-16 02:22:06 JST sby1 LOG: selected new timeline ID: 2
hrk:head-pgsql postgres$ 2013-07-16 02:22:06 JST sby1 LOG: archive
recovery complete
TRAP: FailedAssertion("!(readOff == (XLogCtl->xlblocks[firstIdx] -
8192) % ((uint32) (16 * 1024 * 1024)))", File: "xlog.c", Line: 7048)
2013-07-16 02:22:12 JST sby1 LOG: startup process (PID 37115) was
terminated by signal 6: Abort trap
2013-07-16 02:22:12 JST sby1 LOG: terminating any other active server processes

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-07-15 17:32:23 Re: mvcc catalo gsnapshots and TopTransactionContext
Previous Message Robert Haas 2013-07-15 17:20:44 Re: Add regression tests for SET xxx