Re: Proposal: GetOldestXminExtend for ignoring arbitrary vacuum flags

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: "Seki, Eiji" <seki(dot)eiji(at)jp(dot)fujitsu(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: GetOldestXminExtend for ignoring arbitrary vacuum flags
Date: 2017-02-24 06:34:58
Message-ID: CAMsr+YEwxx5sCPY=+aHw+uSSyNO4SC_-NJzxhCCgrUV+ATFwGQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 14 February 2017 at 14:19, Seki, Eiji <seki(dot)eiji(at)jp(dot)fujitsu(dot)com> wrote:
> Hi all,
>
> I propose the patch that adds a function GetOldestXminExtended that is like GetOldestXmin but can ignore arbitrary vacuum flags. And then, rewrite GetOldestXmin to use it. Note that this is done so as not to change the behavior of GetOldestXmin.

FWIW, I have changes in the logical decoding on standby patch that
also need to extend GetOldestXmin. Specifically, I need to be able to
return the catalog_xmin separately, rather than the current behaviour
of returning what's effectively min(xmin,catalog_xmin).

It's only loosely related to this change, but may be relevant.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-02-24 06:47:44 Re: Poor memory context performance in large hash joins
Previous Message Robert Haas 2017-02-24 06:28:46 Re: case_preservation_and_insensitivity = on