Eelco Dolstra d8cc0bbb5d * Make the "latest succeeded" query (used by the "latest" channel) ...

faster, from about 4.5s to 1.0s for the global "latest" channel.
  Note that the query is only fast if the "IndexBuildsOnJob" and
  "IndexBuildsOnJobAndIsCurrent" indices are dropped - if they exist,
  PostgreSQL will use those instead of the more efficient
  "IndexBuildsOnJobFinishedId" index.  Looks like a bug in the planner
  to me...

2010-02-12 14:49:32 +00:00

..

AddBuilds.pm

Set $NIX_PREFETCH_GIT_DEEP_CLONE.

2010-01-25 13:26:37 +00:00

CatalystUtils.pm

* Make the "latest succeeded" query (used by the "latest" channel)

2010-02-12 14:49:32 +00:00

Nix.pm

* Refactoring: move fetchInput out of hydra_scheduler into a separate

2009-10-26 15:39:14 +00:00