Re: pg_rewarm status - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_rewarm status
Date
Msg-id CA+Tgmoaa4ZvddFpiSUBhEcwAapXJR03R0QKt4GiOqsdV5Gq3-g@mail.gmail.com
Whole thread Raw
In response to Re: pg_rewarm status  (Jim Nasby <jim@nasby.net>)
Responses Re: pg_rewarm status
List pgsql-hackers
On Tue, Dec 17, 2013 at 11:02 AM, Jim Nasby <jim@nasby.net> wrote:
> On 12/17/13, 8:34 AM, Robert Haas wrote:
>>
>> On Tue, Dec 17, 2013 at 12:09 AM, Amit Kapila <amit.kapila16@gmail.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?
>
>
> We've had to manually code something that runs EXPLAIN ANALYZE SELECT * from
> a bunch of tables to warm our caches after a restart, but there's numerous
> flaws to that approach obviously.
>
> Unfortunately, what we really need to warm isn't the PG buffers, it's the FS
> cache, which I suspect this won't help. But I still see where just
> pg_buffers would be useful for a lot of folks, so +1.

It'll do either one.  For the FS cache, on Linux, you can also use pgfincore.

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



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: SSL: better default ciphersuite
Next
From: Tom Lane
Date:
Subject: Re: patch: make_timestamp function