From: | Alex Shulgin <ash(at)commandprompt(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps |
Date: | 2014-12-04 14:16:52 |
Message-ID: | 87d27z4i0b.fsf@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> On 12/03/2014 04:54 PM, Alvaro Herrera wrote:
>> ir commit timestamp directly as they commit,
>> or an external transaction c
>
> Sorry, I'm late to the party, but here's some random comments on this
> after a quick review:
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
--
Alex
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-12-04 14:35:56 | Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps |
Previous Message | Heikki Linnakangas | 2014-12-04 12:26:46 | Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-12-04 14:26:02 | Re: New wal format distorts pg_xlogdump --stats |
Previous Message | Michael Paquier | 2014-12-04 13:51:02 | Re: Add shutdown_at_recovery_target option to recovery.conf |