From: Antoine <melser.anton@gmail.com>
To: me@alternize.com <me@alternize.com>
Cc: Christopher Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: new to postgres (and db management) and performance already a problem :-(
Date: Tue, 17 Jan 2006 09:14:27 +0100
Message-ID: <92d3a4950601170014m352c75bes@mail.gmail.com> (raw)
In-Reply-To: <074b01c61b1c$538335e0$6402a8c0@iwing>
References: <43CC1938.7020807@gmail.com>
<18875.1137451410@sss.pgh.pa.us>
<070501c61aee$ed450560$6402a8c0@iwing>
<22960.1137460135@sss.pgh.pa.us>
<071801c61b05$7ea50c10$6402a8c0@iwing>
<m3hd83sdyw.fsf@mobile.int.cbbrowne.com>
<074b01c61b1c$538335e0$6402a8c0@iwing>
On 17/01/06, me@alternize.com <me@alternize.com> wrote:
>
> > Try a), b), and c) in order on the "offending" tables as they address
> > the problem at increasing cost...
>
> thanks alot for the detailed information! the entire concept of vacuum
> isn't
> yet that clear to me, so your explanations and hints are very much
> appreciated. i'll defenitely try these steps this weekend when the next
> full
> vacuum was scheduled :-)
Thanks guys, that pretty much answered my question(s) too. I have a sneaking
suspicion that vacuuming won't do too much for us however... now that I
think about it - we do very little removing, pretty much only inserts and
selects. I will give it a vacuum full and see what happens.
Cheers
Antoine
--
This is where I should put some witty comment.
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, me@alternize.com, cbbrowne@acm.org
Subject: Re: new to postgres (and db management) and performance already a problem :-(
In-Reply-To: <92d3a4950601170014m352c75bes@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