Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps

From: Alex Shulgin <ash(at)commandprompt(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps
Date: 2014-12-04 14:39:22
Message-ID: 877fy74gyt.fsf@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers


Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:

> Alex Shulgin wrote:
>
>> Also this commit breaks initdb of `make check' for me:
>>
>> creating template1 database in
>> /home/ash/build/postgresql/HEAD/src/test/regress/./tmp_check/data/base/1
>> ... TRAP: FailedAssertion("!(((xmax) >= ((TransactionId) 3)))",
>> File:
>> "/home/ash/src/postgresql/src/backend/storage/ipc/procarray.c",
>> Line: 1414)
>> Aborted (core dumped)
>> child process exited with exit code 134
>
> Uh, that's odd. Can you please get a stack trace? Do you have unusual
> settings or a patched build?

Not really, and I would mention that. Will get a trace.

--
Alex

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Alex Shulgin 2014-12-04 14:50:24 Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps
Previous Message Alvaro Herrera 2014-12-04 14:35:56 Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Shulgin 2014-12-04 14:50:24 Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps
Previous Message Heikki Linnakangas 2014-12-04 14:38:45 Re: make check-world regress failed