Re: problem with pg_statistics - Mailing list pgsql-performance

From Manfred Koizar
Subject Re: problem with pg_statistics
Date
Msg-id 555ofvopbsuiog6tti32natah0futga7d4@4ax.com
Whole thread Raw
In response to Re: problem with pg_statistics  (Andre Schubert <andre@km3.de>)
List pgsql-performance
On Fri, 27 Jun 2003 11:10:58 +0200, Andre Schubert <andre@km3.de>
wrote:
>Once a month we delete the all data of the oldest month.
>And after that a vacuum full verbose analyze is performed.
>Could this cause reordering of the data ?

I may be wrong, but I think VACUUM FULL starts taking tuples from the
end of the relation and puts them into pages at the beginning until
read and write position meet somewhere in the middle.  This explains
the bad correlation.

>And should i do a cluster idx_ts tbl_traffic ?

I think so.

>> >#effective_cache_size = 1000  # default in 8k pages
>>
>> This is definitely too low.  With 512MB or more I tend to set this to
>> ca. 80% of available RAM.  Use top and free to find hints for good
>> values.
>>
>
>Ok, i will talk with my coworker ( he is the sysadmin of our machine )
>and look if can use such amount of RAM, because there are several other
>processes that are running on these machines.
>But i will test and report ...

effective_cache_size does not *control* resource consumption,  it just
*reports* it as a hint to the planner.

Servus
 Manfred

pgsql-performance by date:

Previous
From: Andre Schubert
Date:
Subject: Re: problem with pg_statistics
Next
From: "Bruno BAGUETTE"
Date:
Subject: Large querie with several EXISTS which will be often runned