[PATCH 07/14] Introduce InvalidCommandId and declare that to be the new maximum for CommandCounterIncrement - Mailing list pgsql-hackers

From Andres Freund
Subject [PATCH 07/14] Introduce InvalidCommandId and declare that to be the new maximum for CommandCounterIncrement
Date
Msg-id 1352942234-3953-7-git-send-email-andres@2ndquadrant.com
Whole thread Raw
In response to logical changeset generation v3  (andres@anarazel.de (Andres Freund))
List 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

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: [PATCH 14/14] design document v2.3 and snapshot building design doc v0.2
Next
From: Andres Freund
Date:
Subject: [PATCH 10/14] Allow walsender's to connect to a specific database