Re: Why vacuum?

From: "Martin A(dot) Marques" <martin(at)math(dot)unl(dot)edu(dot)ar>
To: "xuyifeng" <xyf(at)stocke(dot)com>, "bpalmer" <bpalmer(at)crimelabs(dot)net>, <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Why vacuum?
Date: 2000-12-14 12:01:59
Message-ID: 00121409015900.02491@math.unl.edu.ar
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

El Mié 13 Dic 2000 22:24, xuyifeng escribió:
> I have this nasty problem too, in early time, I don't know the problem,
> but we used it for a while, than we found our table growing too fast
> without insert any record( we use update), this behaviour most like M$
> MSACCESS database I had used a long time ago which don't reuse deleted
> record space and full fill your hard disk after several hours, the nasty
> vaccum block any other users to operate on table, this is a big problem
> for a large table, because it will block tooo long to let other user to run
> query. we have a project affected by this problem, and sadly we decide to
> use closure source database - SYBASE on linux, we havn't any other
> selections. :(
>
> note that SYBASE and Informix both have 'update statistics' command, but
> they run it fast in seconds, not block any other user, this is pretty. ya,
> what's good technology!

I have to say that 'update statistics' does not take a few seconds if the
databases have grownto be a bit large. At least thats what I have seen.

Saludos... :-)

--
System Administration: It's a dirty job,
but someone told I had to do it.
-----------------------------------------------------------------
Martín Marqués email: martin(at)math(dot)unl(dot)edu(dot)ar
Santa Fe - Argentina http://math.unl.edu.ar/~martin/
Administrador de sistemas en math.unl.edu.ar
-----------------------------------------------------------------

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2000-12-14 12:02:24 Re: Bug in FOREIGN KEY
Previous Message Denis Perchine 2000-12-14 11:57:32 Re: Why vacuum?