pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas Pundt <mlists@rp-online.de>
To: pgsql-admin@postgresql.org
Cc: BRAHMA PRAKASH TIWARI <prakashr2n5@gmail.com>
Cc: Francesco Andreozzi <francesco.andreozzi@gamestorm.it>
Subject: Re: tuning tips, speed problem
Date: Mon, 19 Jan 2009 14:12:06 +0100
Message-ID: <200901191412.07048.mlists@rp-online.de> (raw)
In-Reply-To: <2acc2c820901190435m4062f8d3v1e6099f32ed009af@mail.gmail.com>
References: <20090116161802.v6tj5jmhw0c80sow@webmail.gamestorm.it>
	<2acc2c820901190435m4062f8d3v1e6099f32ed009af@mail.gmail.com>

On Montag, 19. Januar 2009, BRAHMA PRAKASH TIWARI wrote:
| most probabely this is due to the auto vacuum option on and if auto vacuum
| is on then the in condition of high transaction on database it slows the
| speed of the hole database.Set it off in postgres.conf and vacuum and
| reindex transactional tables manualy with in  every two million
| transactions.
| like
| vacuum full <table name>;
| reindex table <table name>;

Please, a "vacuum full" should only be a measure of last resort ever.
Regular vacuum (without the "full" keyword) should always be enough. 
And I don't recommend turning autovacuum off. 

You might need to increase the "max_fsm_pages" setting to avoid 
database bloat. The output of a database wide "vacuum verbose" should
tell you, if it is set appropriately.

And Francesco, if you say 

  "but on a mysql to execute a simple select with an order by the time was jus
  1 or 2 seconds ... on this installation the time it's about 10 seconds or
  more", 

could you provide the "explain analyze"-output for those queries? This should
help analyzing your problems.

Ciao,
Thomas

-- 
Thomas Pundt <thomas.pundt@rp-online.de> ---- http://rp-online.de/ ----



view thread (7+ messages)  latest in thread

Message-ID: <200901191412.07048.mlists@rp-online.de>
Permalink:  ../200901191412.07048.mlists@rp-online.de/
Also on:    postgresql.org/message-id/200901191412.07048.mlists@rp-online.de

 · 

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-admin@postgresql.org
  Cc: mlists@rp-online.de, prakashr2n5@gmail.com, francesco.andreozzi@gamestorm.it
  Subject: Re: tuning tips, speed problem
  In-Reply-To: <200901191412.07048.mlists@rp-online.de>

* 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