pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Manfred Koizar <mkoi-pg@aon.at>
To: Andre Schubert <andre@km3.de>
Cc: tgl@sss.pgh.pa.us
Cc: pgsql-performance@postgresql.org
Subject: Re: problem with pg_statistics
Date: Fri, 27 Jun 2003 12:05:14 +0200
Message-ID: <555ofvopbsuiog6tti32natah0futga7d4@4ax.com> (raw)
In-Reply-To: <20030627111058.08f71b14.andre@km3.de>
References: <20030626151515.5fd0faf0.andre@km3.de>
	<24083.1056636485@sss.pgh.pa.us>
	<h64mfv8quqjc19dv0ufm9oegj6p1rpeipp@4ax.com>
	<25814.1056643432@sss.pgh.pa.us>
	<20030627080735.66d6bdf0.andre.schubert@km3.de>
	<4avnfvkjr8q7cl8ac6f01j8rddj4pjlte0@4ax.com>
	<20030627111058.08f71b14.andre@km3.de>

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



view thread (9+ messages)

Message-ID: <555ofvopbsuiog6tti32natah0futga7d4@4ax.com>
Permalink:  ../555ofvopbsuiog6tti32natah0futga7d4@4ax.com/
Also on:    postgresql.org/message-id/555ofvopbsuiog6tti32natah0futga7d4@4ax.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: mkoi-pg@aon.at, andre@km3.de, tgl@sss.pgh.pa.us
  Subject: Re: problem with pg_statistics
  In-Reply-To: <555ofvopbsuiog6tti32natah0futga7d4@4ax.com>
  References: <20030626151515.5fd0faf0.andre@km3.de> <24083.1056636485@sss.pgh.pa.us> <h64mfv8quqjc19dv0ufm9oegj6p1rpeipp@4ax.com> <25814.1056643432@sss.pgh.pa.us> <20030627080735.66d6bdf0.andre.schubert@km3.de> <4avnfvkjr8q7cl8ac6f01j8rddj4pjlte0@4ax.com> <20030627111058.08f71b14.andre@km3.de> <555ofvopbsuiog6tti32natah0futga7d4@4ax.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox