Re: pg_rewarm status

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jim Nasby <jim(at)nasby(dot)net>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Jeff Amiel <becauseimjeff(at)yahoo(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_rewarm status
Date: 2013-12-17 16:45:51
Message-ID: CA+Tgmoaa4ZvddFpiSUBhEcwAapXJR03R0QKt4GiOqsdV5Gq3-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 17, 2013 at 11:02 AM, Jim Nasby <jim(at)nasby(dot)net> wrote:
> On 12/17/13, 8:34 AM, Robert Haas wrote:
>>
>> 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?
>
>
> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-12-17 16:46:10 Re: patch: make_timestamp function
Previous Message Bruce Momjian 2013-12-17 16:26:13 Re: SSL: better default ciphersuite