[PATCH 07/14] Introduce InvalidCommandId and declare that to be the new maximum for CommandCounterIncrement

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: [PATCH 07/14] Introduce InvalidCommandId and declare that to be the new maximum for CommandCounterIncrement
Date: 2012-11-15 01:17:07
Message-ID: 1352942234-3953-7-git-send-email-andres@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


This is useful to be able to represent a CommandId thats invalid. There was no
such value before.

This decreases the possible number of subtransactions by one which seems
unproblematic. Its also not a problem for pg_upgrade because cmin/cmax are
never looked at outside the context of their own transaction (spare timetravel
access, but thats new anyway).
---
src/backend/access/transam/xact.c | 4 ++--
src/include/c.h | 1 +
2 files changed, 3 insertions(+), 2 deletions(-)

Attachment Content-Type Size
0007-Introduce-InvalidCommandId-and-declare-that-to-be-th.patch text/x-patch 1022 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2012-11-15 01:17:08 [PATCH 08/14] Store the number of subtransactions in xl_running_xacts separately from toplevel xids
Previous Message Andres Freund 2012-11-15 01:17:06 [PATCH 06/14] Add a new function pg_relation_by_filenode to lookup up a relation given the tablespace and the filenode OIDs