Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch

[ time to move this thread to -hackers ]

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>>> Heikki Linnakangas wrote:
>>>> Tom Lane wrote:
>>>>> BTW, I don't care much for the terminology "phantom cid" ... there's
>>>>> nothing particularly "phantom" about them, seeing they get onto disk.
>>>>> Can anyone think of a better name? The best I can do offhand is
>>>>> "merged cid" or "cid pair", which aren't inspiring.

>>>> MultiCid, like the MultiXacts? Maybe not, they're quite different beasts...

>>> Dual cid? Double cid?

>> "Double cid" doesn't sound too bad. Another thought that just came to
>> mind is "cid interval" or some variant of that.

> I don't like "double ctid" because it is really just one ctid, but
> represents two. I am thinking "packed ctid" is the right wording. It
> doesn't have the same impact as "phantom", but it is probably better.

Packed doesn't seem to have quite the right connotation either --- it
sounds like it means there are two separable fields in the CID value.

Maybe "composite cid"?

Another issue that we need to think about before we go too far with this
is the problem that we punted on before 8.2 release: how to deal with
rolling back an upgrade of a row-level lock from shared to exclusive
within a subtransaction. I'm a bit nervous about committing to merging
cmin and cmax before we have an idea how we're going to solve that ---
it might foreclose a solution. Or maybe we could piggyback on phantom/
composite/whatever CIDs to solve it, which would be great, but let's
try to sketch out a solution now.

regards, tom lane