From: | "MauMau" <maumau307(at)gmail(dot)com> |
---|---|
To: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | "Jeff Janes" <jeff(dot)janes(at)gmail(dot)com>, "Jeff Amiel" <becauseimjeff(at)yahoo(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_rewarm status |
Date: | 2013-12-17 20:31:47 |
Message-ID: | 10FA5430C28A40F7BBD17E84B98438B6@maumau |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: "Robert Haas" <robertmhaas(at)gmail(dot)com>
> On Tue, Dec 17, 2013 at 12:09 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
> wrote:
>> I have used pg_prewarm during some of work related to Buffer Management
>> and
>> other performance related work. It is quite useful utility.
>> +1 for reviving this patch for 9.4
>
> 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.
Regards
MauMau
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-12-17 20:33:41 | Re: pg_rewarm status |
Previous Message | Marko Kreen | 2013-12-17 20:26:48 | Re: SSL: better default ciphersuite |