Re: git push hook to check for outdated timestamps - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: git push hook to check for outdated timestamps
Date
Msg-id 20150624135237.GE3289@postgresql.org
Whole thread Raw
In response to Re: git push hook to check for outdated timestamps  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
Noah Misch wrote:
> On Sun, Jun 14, 2015 at 12:37:00PM +0200, Magnus Hagander wrote:

> > Would we in that case want to enforce linearity *and* recent-ness, or just
> > linearity? as in, do we care about the commit time even if it doesn't
> > change the order?
> 
> If a recency check is essentially free, let's check both.  Otherwise,
> enforcing linearity alone is a 95% solution that implicitly bounds recency.

Should there also be a check to reject times too far in the future?  I
think a clock skew of a few minutes (up to ten?) is acceptable, but more
than that would cause trouble for other committers later on.

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



pgsql-hackers by date:

Previous
From: Kohei KaiGai
Date:
Subject: Re: Foreign join pushdown vs EvalPlanQual
Next
From: Robert Haas
Date:
Subject: Re: Multixid hindsight design