Re: pg_prewarm

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_prewarm
Date: 2012-03-09 16:40:49
Message-ID: CA+Tgmoa1APwZ3QqS-yg6+f5SVdrAmi6JdgbpG4r5mJ8W+ky2Ug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 9, 2012 at 10:53 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Fri, Mar 9, 2012 at 5:21 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Fri, Mar 9, 2012 at 5:24 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>>> When a relation is loaded into cache, are corresponding indexes also loaded
>>> at the same time?
>>
>> No, although if you wanted to do that you could easily do so, using a
>> query like this:
>>
>> select pg_prewarm(indexrelid, 'main', 'read', NULL, NULL) from
>> pg_index where indrelid = 'your_table_name'::regclass;
>
> Could that be included in an example?  Maybe admins are expected to
> know how to construct such queries of the cuff, but I always need to
> look it up each time which is rather tedious.

Not a bad idea. I thought of including an "Examples" section, but it
didn't seem quite worth it for the simple case of prewarming a heap.
Might be worth it to also include this.

> In the patch:
>
> s/no special projection/no special protection/

OK, will fix.

> Thanks for putting this together.

I will confess that it was 0% altruistic. Not having it was ruining
my day. :-)

--
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 David E. Wheeler 2012-03-09 17:02:01 Re: elegant and effective way for running jobs inside a database
Previous Message Bruce Momjian 2012-03-09 16:33:36 Re: pg_upgrade and umask