Re: Failed to delete old ReorderBuffer spilled files - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Failed to delete old ReorderBuffer spilled files
Date
Msg-id 20180105153023.seas4iankjpiwjyf@alvherre.pgsql
Whole thread Raw
In response to Re: Failed to delete old ReorderBuffer spilled files  (atorikoshi <torikoshi_atsushi_z2@lab.ntt.co.jp>)
Responses Re: Failed to delete old ReorderBuffer spilled files
List pgsql-hackers
atorikoshi wrote:

> > FYI "make check" in contrib/test_decoding fails a couple of isolation
> > tests, one with an assertion failure for my automatic patch tester[1].
> > Same result on my laptop:
> > 
> > test ondisk_startup           ... FAILED (test process exited with exit code 1)
> > test concurrent_ddl_dml       ... FAILED (test process exited with exit code 1)
> > 
> > TRAP: FailedAssertion("!(!dlist_is_empty(head))", File:
> > "../../../../src/include/lib/ilist.h", Line: 458)
> 
> Thanks for letting me know.
> I think I only tested running "make check" at top directory, sorry
> for my insufficient test.
> 
> The test failure happened at the beginning of replication(creating
> slot), so there are no changes yet and getting the tail of changes
> failed.
> 
> Because the bug we are fixing only happens after creating files,
> I've added "txn->serialized" to the if statement condition.

Ahh, so the reason I didn't see these crashes is that Atsushi had
already fixed them.  Nice.  It would be *very* good to trim the quoted
material when you reply --- don't leave everything, just enough lines
for context.  I would have seen this comment if it didn't require me to
scroll pages and pages and pages of useless material.

I have pushed this patch from 9.4 to master.  I reformulated the
comments.

This is an "implicitly aborted transaction":

alvherre=# create table implicit (a int);
CREATE TABLE
Duración: 0,959 ms
alvherre=# insert into implicit select 1/i from generate_series(5, -5, -1) i;
ERROR:  division by zero

Note there is no explicit ABORT here, so it is implicit.

But that is not what you were trying to say.  The term "crashed
transaction" seems to me to convey the meaning better, so I used that.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Condition variable live lock
Next
From: Tom Lane
Date:
Subject: Re: setting estate in ExecInitNode() itself