From: | Marc Mamin <M(dot)Mamin(at)intershop(dot)de> |
---|---|
To: | Andy Colson <andy(at)squeakycode(dot)net> |
Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Index Only Scan vs Cache |
Date: | 2015-07-14 18:19:51 |
Message-ID: | B6F6FD62F2624C4C9916AC0175D56D8828C03EE5@jenmbs01.ad.intershop.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>On 7/9/2015 12:41 PM, Tom Lane wrote:
>> Andy Colson <andy(at)squeakycode(dot)net> writes:
>>> My question is: Will PG cache only the index (assuming it can always do
>>> an Index Only Scan), or will it cache the table as well?
I'm not sure that indexes on tiny tables are useful.
They raise the options to consider by the query planner, which has its small cost too.
I'd be interested on other opinions on this.
Any rule of the thumb with which number of pages per relation it is worth to start indexing ?
And still another question: I've have tiny static tables too, that never got analyzed.
Can this fool the query planner in a negative way ?
regards,
Marc Mamin
>> The table blocks would fall out of cache if they're never touched.
>>
>> regards, tom lane
>>
>>
>
>Sweet! Thanks Tom.
>
>
>--
>Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-07-14 18:41:58 | Re: timestamp check |
Previous Message | Marc Mamin | 2015-07-14 18:02:22 | Re: Creating table with data from a join |