pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Antoine <melser.anton@gmail.com>
To: mischa@ca.sophos.com
Cc: pgsql-performance@postgresql.org
Subject: Re: vacuuming problems continued
Date: Wed, 7 Jun 2006 22:52:26 +0200
Message-ID: <92d3a4950606071352u7aa25789q9f1dbc57fd14847e@mail.gmail.com> (raw)
In-Reply-To: <4485D9A1.30807@ca.sophos.com>
References: <92d3a4950606010454y67293765o56001e8996975b45@mail.gmail.com>
	<20060605204151.GC7071@phlogiston.dyndns.org>
	<4485CECC.4040207@ca.sophos.com>
	<4485D5C3.7010803@commandprompt.com>
	<4485D9A1.30807@ca.sophos.com>

Hi all and thanks for your responses. I haven't yet had a chance to
tweak the autovac settings but I really don't think that things can be
maxing out even the default settings.
We have about 4 machines that are connected 24/7 - they were doing
constant read/inserts (24/7) but that was because the code was
rubbish. I managed to whinge enough to get the programme to read, do
the work, then insert, and that means they are accessing (connected
but idle) for less than 5% of the day. We have about another 10
machines that access (reads and updates) from 8-5. It is running on a
P4 with 256 or 512meg of ram and I simply refuse to believe this load
is anything significant... :-(.
There are only two tables that see any action, and the smaller one is
almost exclusively inserts.
Much as I believe it shouldn't be possible the ratio of 5:1 for the db
vs fresh copy has given me a taste for a copy/drop scenario...
I will try and increase settings and keep you posted.
Cheers
Antoine


-- 
This is where I should put some witty comment.



view thread (9+ messages)  latest in thread

Message-ID: <92d3a4950606071352u7aa25789q9f1dbc57fd14847e@mail.gmail.com>
Permalink:  ../92d3a4950606071352u7aa25789q9f1dbc57fd14847e@mail.gmail.com/
Also on:    postgresql.org/message-id/92d3a4950606071352u7aa25789q9f1dbc57fd14847e@mail.gmail.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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: melser.anton@gmail.com, mischa@ca.sophos.com
  Subject: Re: vacuuming problems continued
  In-Reply-To: <92d3a4950606071352u7aa25789q9f1dbc57fd14847e@mail.gmail.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