From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(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 15:53:22 |
Message-ID: | CAMkU=1xOSTpT8=VLcghcYQE6xR0Paqm-iwNcp=dZ81rdLgVKQQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
In the patch:
s/no special projection/no special protection/
Thanks for putting this together.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2012-03-09 15:55:27 | Re: elegant and effective way for running jobs inside a database |
Previous Message | Robert Haas | 2012-03-09 15:50:05 | Re: pg_prewarm |