On 28 Aug 2001, Doug McNaught wrote:
> You obviously know what you're doing, but are you absolutely sure one
> of your clients isn't holding a transaction open? That'll hang vacuum
> every time...
Yup. We wrote the client that is accessing the database. It's using
PHP, and we don't even *use* transactions currently. But that isn't the
problem. From what I gather so far, the server is under fairly high
load (6 right now) so vacuuming the database (520MB in files, 5MB dump)
takes a *long* time. While it's vacuuming, anything using that database
just has to wait, and that's our problem.
Actually, on a whim, I dumped that 520MB database to it's 5MB file, and
reimported it into an entirely new DB. It was 14MB. We vacuum at least
once an hour (we have a loader that runs every hour, it may run multiple
concurrent insert scripts). We also use vacuum analyze. So, I really
can't see a reason for it to balloon to that horridly expanded size.
Maybe stale indexes? Aborted vacuums? What on earth would cause that?
--
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
| Shaun M. Thomas INN Database Programmer |
| Phone: (309) 743-0812 Fax : (309) 743-0830 |
| Email: [EMAIL PROTECTED] AIM : trifthen |
| Web : hamster.lee.net |
| |
| "Most of our lives are about proving something, either to |
| ourselves or to someone else." |
| -- Anonymous |
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
