Skip site navigation (1) Skip section navigation (2)

Re: why the DB file size does not reduce when 'delete'the data in DB?

From: "xuyifeng" <jamexu(at)telekbird(dot)com(dot)cn>
To: "Roberto Mello" <rmello(at)cc(dot)usu(dot)edu>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: why the DB file size does not reduce when 'delete'the data in DB?
Date: 2001-03-04 07:15:18
Message-ID: 000901c0a47a$e03c7dc0$cc01a8c0@xyf (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-sql
----- Original Message ----- 
From: Roberto Mello <rmello(at)cc(dot)usu(dot)edu>
To: xuyifeng <jamexu(at)telekbird(dot)com(dot)cn>
Sent: Sunday, March 04, 2001 10:40 AM
Subject: Re: [HACKERS] why the DB file size does not reduce when 'delete'the data in DB?

> On Sun, Mar 04, 2001 at 10:01:37AM +0800, xuyifeng wrote:
> > 
> > could anyone remove this nasty bug in 7.2? this is already a big pain and is the reason 
> > why am I still using MySQL in my product server. another nasty thing is it does not 
> > allow me to reference table in another database.  sigh.
> I don "vacuum analyze" in my Postgres database every night very easily
> using a simple cron job. I create the cron job and forget about it. Really
> it's not that hard don't you think?
> Sure, it's not the desired way, but that's not big enough a reason to
> use PostgreSQL. I could think of a dozen reasons that counter that one and
> would favor PostgreSQL in technical terms. Compared to those, this is
> really really a minor issue.
> As to referring to a table in another DB, I don't know when is that
> going to be implemented.
> -Roberto
> -- 
> +----| USU Free Software & GNU/Linux Club|------+
>   Roberto Mello - Computer Science, USU - 
> - Space Dynamics Lab, Web Developer    
> << Politically Un-Correct Tagline Deleted! >>

I know your situations,  your DB is not updated and inserted lots of records in few minutes,
mine is difference,  I have a real time Stock Trading  system, you know, stock, its price 
is changed every minute or even every second ,  I need update and insert delta change into DB,  
draw their trend graphics,  suppose there are 3000 stocks in market,  there maybe 9000 records 
changed and inserted in one minutes, because PGSQL's storage manager problem( it does not 
reuse deleted record space),  in 4 hours trading period,  my harddisk can be full filled.  because in 
the period, the table indeed gets very large, doing VACCUME is impossible in realtime, it will lock
out other clients too long time,  my point of view is PGSQL is fit for static or small changed database, 
not fit for lots of change in short time.

Xu Yifeng

In response to


pgsql-hackers by date

Next:From: Matthew KirkwoodDate: 2001-03-04 12:17:59
Subject: Multi-process pgbench?
Previous:From: The Hermit HackerDate: 2001-03-04 03:05:29
Subject: Re: [HACKERS] why the DB file size does not reduce when 'delete'the data in DB?

pgsql-sql by date

Next:From: Boulat KhakimovDate: 2001-03-04 17:01:28
Subject: How to describe a field in the table ???
Previous:From: Gerald GutierrezDate: 2001-03-04 04:37:42

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group