Re: lcr v5 - introduction of InvalidCommandId - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: lcr v5 - introduction of InvalidCommandId
Date
Msg-id CAM3SWZRS4gwcisAWrqSfKg=HnN+RpV=JbcZX7drR53QxTChX3g@mail.gmail.com
Whole thread Raw
In response to Re: lcr v5 - introduction of InvalidCommandId  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Thu, Sep 5, 2013 at 11:30 AM, Andres Freund <andres@2ndquadrant.com> wrote:
>> Ideally I'd have made InvalidCommandId = 0 and FirstCommandId = 1,
>> but I suppose we can't have that without an on-disk compatibility break.
>
> The patch actually does change it exactly that way. My argument for that
> being valid is that CommandIds don't play any role outside of their own
> transaction.

Right. It seems like this should probably be noted in the
documentation under "5.4. System Columns" -- I just realized that it
isn't.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: lcr v5 - introduction of InvalidCommandId
Next
From: Blake Smith
Date:
Subject: Re: Hstore: Query speedups with Gin index