Re: snapshot too old, configured by time

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Kevin Grittner <kgrittn(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thom Brown <thom(at)linux(dot)com>, Steve Singer <steve(at)ssinger(dot)info>, Kevin Grittner <kgrittn(at)ymail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: snapshot too old, configured by time
Date: 2016-04-19 17:49:01
Message-ID: 20160419174901.GA728278@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Grittner wrote:
> On Tue, Apr 19, 2016 at 11:02 AM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:

> > Robert Haas wrote:
> >
> >> That wouldn't have fixed my problem, which involved rebasing a patch.
> >
> > True. I note that it's possible to munge a patch mechanically to sort
> > out this situation.
>
> I admit it is possible. I'm becoming more convinced with each post
> that it's the wrong approach. I feel like I have been in the
> modern version of an Æsop fable here:
>
> http://www.bartleby.com/17/1/62.html

LOL.

Well, it seems I'm outvoted. I leave you to do with your donkey as you
please.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2016-04-19 18:00:34 Re: Parser extensions (maybe for 10?)
Previous Message Kevin Grittner 2016-04-19 17:44:27 Re: snapshot too old, configured by time