Re: Fix GetOldestXmin comment

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix GetOldestXmin comment
Date: 2017-05-30 14:07:21
Message-ID: CAA4eK1L08j7Pd1T4AFHZm6t5Yq8Ciy93YXhn9vaBGJJoJJZ2_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 30, 2017 at 6:32 AM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> Hi,
>
> While reading source code, I realized that comment of GetOldestXmin mentions;
>
> * if rel = NULL and there are no transactions running in the current
> * database, GetOldestXmin() returns latestCompletedXid.
>
> However, in that case if I understand correctly GetOldestXmin()
> actually returns latestCompletedXid + 1 as follows;
>

Isn't there another gotcha in above part of the comment, shouldn't it
say rel != NULL? AFAICS, when rel is NULL, it considers all databases
not only current database.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-05-30 14:12:46 Re: [HACKERS] [PATCH] relocation truncated to fit: citus build failure on s390x
Previous Message Robert Haas 2017-05-30 14:02:56 Re: [HACKERS] [PATCH] relocation truncated to fit: citus build failure on s390x