Re: parallel pg_dump causes assertion failure in HEAD - Mailing list pgsql-hackers

From Andres Freund
Subject Re: parallel pg_dump causes assertion failure in HEAD
Date
Msg-id 518b4768-7731-4f05-aa90-525f3b633374@email.android.com
Whole thread Raw
In response to parallel pg_dump causes assertion failure in HEAD  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: parallel pg_dump causes assertion failure in HEAD
List pgsql-hackers
On March 5, 2014 6:07:43 PM CET, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>$ pg_dump -F d -j 4 -f foo regression
>pg_dump: [archiver (db)] query failed: pg_dump: [parallel archiver]
>query was: SET TRANSACTION SNAPSHOT '00002130-1'
>pg_dump: [archiver (db)] query failed: pg_dump: [archiver (db)] query
>failed: pg_dump: [archiver (db)] query failed: $
>
>postmaster log shows:
>
>TRAP: FailedAssertion("!(HistoricSnapshotActive())", File: "snapmgr.c",
>Line: 355)
>TRAP: FailedAssertion("!(HistoricSnapshotActive())", File: "snapmgr.c",
>Line: 355)
>TRAP: FailedAssertion("!(HistoricSnapshotActive())", File: "snapmgr.c",
>Line: 355)
>TRAP: FailedAssertion("!(HistoricSnapshotActive())", File: "snapmgr.c",
>Line: 355)
>LOG:  server process (PID 15069) was terminated by signal 6: Aborted
>DETAIL:  Failed process was running: SET TRANSACTION SNAPSHOT
>'00002130-1'
>LOG:  terminating any other active server processes
>
>That Assert appears to have been introduced by commit b89e1510.

It's a typo. It should make sure there is *no* historical snapshot. Will later test if it really works, but I'd be
surprisedif not.
 

Andres

-- 
Please excuse brevity and formatting - I am writing this on my mobile phone.

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



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: jsonb and nested hstore
Next
From: Stephen Frost
Date:
Subject: Re: jsonb and nested hstore