Re: 9.4 logical decoding assertion

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Steve Singer <steve(at)ssinger(dot)info>
Cc: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 9.4 logical decoding assertion
Date: 2014-08-15 13:42:08
Message-ID: 20140815134208.GM28805@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2014-08-14 16:03:08 -0400, Steve Singer wrote:
> I hit the following on 9.4 testing logical decoding.
>
>
> TRAP: FailedAssertion("!(prev_first_lsn < cur_txn->first_lsn)", File:
> "reorderbuffer.c", Line: 618)
> LOG: server process (PID 3801) was terminated by signal 6: Aborted

I saw that recently while hacking around, but I thought it was because
of stuff I'd added. But apparently not.

Hm. I think I see how that might happen. It might be possible (and
harmless) if two subxacts of the same toplevel xact have the same
first_lsn. But if it's not just <= vs < it'd be worse.

> Unfortunately I don't have a core file and I haven't been able to reproduce
> this.

Any information about the workload? Any chance you still have the data
directory around?

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-08-15 13:54:01 Re: Reporting the commit LSN at commit time
Previous Message Fujii Masao 2014-08-15 13:40:59 Re: [PATCH] Fix search_path default value separator.