Re: advance local xmin more aggressively

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: advance local xmin more aggressively
Date: 2015-01-16 23:15:10
Message-ID: 54B99B7E.1050500@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/15/2015 09:57 PM, Robert Haas wrote:
> On Thu, Jan 15, 2015 at 3:08 AM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>> On Mon, Dec 22, 2014 at 7:31 PM, Heikki Linnakangas
>> <hlinnakangas(at)vmware(dot)com> wrote:
>>> Here's an updated version, rebased over the pairing heap code that I just
>>> committed, and fixing those bugs.
>> So, are we reaching an outcome for the match happening here?
>
> Well, I still like using the existing ResourceOwner pointers to find
> the snapshots more than introducing a separate data structure just for
> that. But I'm OK with Heikki committing his version and, if anybody
> notices the new code becoming a hotspot, we can revisit the issue.

Ok, committed.

- Heikki

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2015-01-16 23:20:00 Re: hung backends stuck in spinlock heavy endless loop
Previous Message Andres Freund 2015-01-16 23:02:36 Re: Logical Decoding follows timelines