Re: pg_rewarm status - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_rewarm status
Date
Msg-id CA+TgmoY5id82KZuc01CvxG5+9E1+4=iCYy5okEo7k0J=8brBMw@mail.gmail.com
Whole thread Raw
In response to Re: pg_rewarm status  ("MauMau" <maumau307@gmail.com>)
Responses Re: pg_rewarm status
List pgsql-hackers
On Tue, Dec 17, 2013 at 3:31 PM, MauMau <maumau307@gmail.com> wrote:
>> Any other votes?
>
> +1
> Some customers requested:
>
> 1. fill the database cache with frequently accessed data before starting or
> resuming service for their users (for the first time or after maintenance
> work), so that they can provide steady and predictable performance.
>
> 2. pin some (reference or master) data in the database cache not to be
> evicted from the cache (like Oracle's KEEP buffer?), for the same reason as
> 1.
>
> I'd love such useful feature like pg_rewarm to be included in core.  I hope
> such nice features won't be rejected just because there are already similar
> external tools.

For the record, the name of the tool is pg_PREwarm, not pg_rewarm.
The subject line of this thread is a typo.

Sounds like it might be worth dusting the patch off again...

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: "MauMau"
Date:
Subject: Re: pg_rewarm status
Next
From: Robert Haas
Date:
Subject: Re: preserving forensic information when we freeze