pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Xu, Xiaoyi (Rocky) FSM <xyxu@northwestern.edu>
Cc: andy.shellam@mailnetwork.co.uk
Cc: pgsql-admin@postgresql.org
Subject: Re: Error in MS Access
Date: Mon, 15 May 2006 15:13:01 -0500
Message-ID: <20060515201301.GK26212@pervasive.com> (raw)
In-Reply-To: <D225C9E264D67D44AD092DC5683D31E403453208@medex2k.fsm.northwestern.edu>
References: <20060515194228.GH26212@pervasive.com>
	<D225C9E264D67D44AD092DC5683D31E403453208@medex2k.fsm.northwestern.edu>

On Mon, May 15, 2006 at 02:55:04PM -0500, Xu, Xiaoyi (Rocky) FSM wrote:
> Jim,
> 
> I will find out the detailed version. Meanwhile /home0 is around 8.6 GB.
> I don't know how large the DB is. Which file or which command I should
> look for? About vacuuming, I don't know either. Can I do vacuuming while
> making DB online? I am helping an internal department whose IT person
> left and for 5 months no one ever managed this Solaris box. All of
> sudden database users began to experience problems with an in-house
> application. 

If it's anything newer than 7.2 (and I really hope it's a *lot* newer
than that), then yes, you can vacuum without locking users out. I know
that at some point you couldn't do that, but I don't know how long ago
that was since I started using PostgreSQL at version 7.2.

I suspect that no one has been vacuuming the database and that it now
has scads of dead rows. It's surprising users haven't been screaming
about it being slow before now if that's the case.

If you search for 'vacuum' at
http://www.pervasivepostgres.com/instantkb13/search.aspx you'll find
some articles that might help you.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (8+ messages)  latest in thread

Message-ID: <20060515201301.GK26212@pervasive.com>
Permalink:  ../20060515201301.GK26212@pervasive.com/
Also on:    postgresql.org/message-id/20060515201301.GK26212@pervasive.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-admin@postgresql.org
  Cc: jnasby@pervasive.com, xyxu@northwestern.edu, andy.shellam@mailnetwork.co.uk
  Subject: Re: Error in MS Access
  In-Reply-To: <20060515201301.GK26212@pervasive.com>
  References: <20060515194228.GH26212@pervasive.com> <D225C9E264D67D44AD092DC5683D31E403453208@medex2k.fsm.northwestern.edu> <20060515201301.GK26212@pervasive.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