Re: 9.4 logical decoding assertion - Mailing list pgsql-hackers

From Andres Freund
Subject Re: 9.4 logical decoding assertion
Date
Msg-id 20140815134208.GM28805@awork2.anarazel.de
Whole thread Raw
In response to 9.4 logical decoding assertion  (Steve Singer <steve@ssinger.info>)
Responses Re: 9.4 logical decoding assertion
List 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



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: [PATCH] Fix search_path default value separator.
Next
From: Tom Lane
Date:
Subject: Re: Reporting the commit LSN at commit time