On March 5, 2014 6:07:43 PM CET, Tom Lane <t...@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 surprised if 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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
