Re: Decrease MAX_BACKENDS to 2^16

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Decrease MAX_BACKENDS to 2^16
Date: 2014-04-26 21:16:46
Message-ID: CAM3SWZSvdpqUgzX+7gHjGi0_fhKN9Q-6F-phBZZpc2eyPMo=Mw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Apr 26, 2014 at 1:58 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> The 2Q paper also suggests a correlated reference period.

I withdraw this. 2Q in fact does not have such a parameter, while
LRU-K does. But the other major system I mentioned very explicitly has
a configurable delay that serves this exact purpose. This "prevents a
burst of pins on a buffer counting as many touches". The point is that
this approach is quite feasible, and may even be the best way of
addressing the general problem of correlated references.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2014-04-27 00:28:11 Re: Decrease MAX_BACKENDS to 2^16
Previous Message Tom Lane 2014-04-26 21:05:21 Re: make check-world problem