Re: [COMMITTERS] pgsql: Avoid pin scan for replay of XLOG_BTREE_VACUUM

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Avoid pin scan for replay of XLOG_BTREE_VACUUM
Date: 2016-01-11 08:14:22
Message-ID: CANP8+jJiJee8+P_SynWXmyqpPTxpgdFKrsP0-uiokQhJQDCNWw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 11 January 2016 at 01:46, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> /me crawls into a hole.
>
> Thanks.

Far from it, thanks very much for thinking about it.

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-01-12 00:55:57 pgsql: Avoid dump/reload problems when using both plpython2 and plpytho
Previous Message Robert Haas 2016-01-11 02:36:03 pgsql: Remove obsolete comment.

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-01-11 11:14:10 Re: Request - repeat value of \pset title during \watch interations
Previous Message Amit Kapila 2016-01-11 06:02:59 Re: checkpointer continuous flushing