Re: Trying to understand page structures in PG

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "'Jeff Janes *EXTERN*'" <jeff(dot)janes(at)gmail(dot)com>, rob stone <floriparob(at)gmail(dot)com>
Cc: Rakesh Kumar *EXTERN* <rakeshkumar464a3(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Trying to understand page structures in PG
Date: 2016-04-08 09:08:01
Message-ID: A737B7A37273E048B164557ADEF4A58B5383C08B@ntex2010i.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jeff Janes wrote:
>> I am curious because of "while xmax is the transaction ID that
>> *removed* the row".
>
> "marked for removal" would be more accurate. If the row were actually
> physically removed, it would no longer have a xmax to set.

Yes, thanks for the clarification.
I was thinking "logically removed", but I realize my wording was confusing.

Yours,
Laurenz Albe

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2016-04-08 09:18:07 Re: Trying to understand page structures in PG
Previous Message Victor Pontis 2016-04-08 00:16:06 Re: [GENERAL] pg_restore casts check constraints differently