pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bill McGonigle <bill@bfccomputing.com>
To: Tatsumi Abe <sc-abe@milan.nri.co.jp>
Cc: pgsql-performance@postgresql.org
Subject: Re: About the relation between fragmentation of file and VACUUM
Date: Thu, 1 Dec 2005 07:44:22 -0500
Message-ID: <c6ef9f5e9b6effd82ee5408096c9cbc2@bfccomputing.com> (raw)
In-Reply-To: <00d101c5f63b$33348330$3cd7adc0@julia>
References: <00d101c5f63b$33348330$3cd7adc0@julia>

On Dec 1, 2005, at 00:50, Tatsumi Abe wrote:

> However, In my current environment I can't stop PostgreSQL and cancel
> fragmentation.
>
> Could anyone advise some solutions for this fragmentation problem
> without stopping PostgreSQL ?

This is somewhat of an aside and intended just as a helpful suggestion 
since I've been in this spot before: if you have this kind of uptime 
requirement the first project to work on is getting the environment to 
the point where you can take out at least one database server at a time 
for maintenance.  You're going to be forced to do this sooner or later 
- whether by disk failure, software error (Pg or OS), user error 
(restore from backup) or security issues (must patch fixes).

So disk fragmentation is a great thing to worry about at some point, 
but IMHO you've got your neck under the guillotine and worrying about 
your cuticles.

I've heard the arguments before, usually around budget, and if the 
company can't spend any money but needs blood-from-stone performance 
tweaks, somebody isn't doing the math right (I'm assuming this isn't 
running on a satellite).  Plus, your blood pressure will go down when 
things are more resilient.  I've tried the superhero thing before and 
it's just not worth it.

-Bill
-----
Bill McGonigle, Owner           Work: 603.448.4440
BFC Computing, LLC              Home: 603.448.1668
bill@bfccomputing.com           Mobile: 603.252.2606
http://www.bfccomputing.com/    Pager: 603.442.1833
Jabber: flowerpt@gmail.com      Text: bill+text@bfccomputing.com
Blog: http://blog.bfccomputing.com/




view thread (5+ messages)

Message-ID: <c6ef9f5e9b6effd82ee5408096c9cbc2@bfccomputing.com>
Permalink:  ../c6ef9f5e9b6effd82ee5408096c9cbc2@bfccomputing.com/
Also on:    postgresql.org/message-id/c6ef9f5e9b6effd82ee5408096c9cbc2@bfccomputing.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: bill@bfccomputing.com, sc-abe@milan.nri.co.jp
  Subject: Re: About the relation between fragmentation of file and VACUUM
  In-Reply-To: <c6ef9f5e9b6effd82ee5408096c9cbc2@bfccomputing.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