Received: from mail2.mx.voyager.net (mail2.mx.voyager.net [216.93.66.201]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f24IcXx65841 for ; Sun, 4 Mar 2001 13:38:33 -0500 (EST) (envelope-from mitch@venux.net) Received: from windows (mdmmi052194.voyager.net [216.93.52.194] (may be forged)) by mail2.mx.voyager.net (8.10.2/8.10.2) with SMTP id f24Ie3n87596; Sun, 4 Mar 2001 13:40:03 -0500 (EST) Message-ID: <00d501c0a4da$21a45ee0$0200000a@windows> From: "Mitch Vincent" To: "xuyifeng" , "Roberto Mello" Cc: References: <008601c0a44f$0d657b20$cc01a8c0@xyf> <20010303194029.A31190@cc.usu.edu> <000901c0a47a$e03c7dc0$cc01a8c0@xyf> Subject: Re: why the DB file size does not reduce when 'delete'the data in DB? Date: Sun, 4 Mar 2001 13:37:11 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200103/48 X-Sequence-Number: 5328 > 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. It's admitadly a problem so I don't think you need to convince everyone that it's not the best way to handle things :-) I hate to say it, but your options currently are to upgrade your storage device or change databases... I think I'd fork out some cash for some new hardware verses buying a commercial database or putting up with the missing features of MySQL.. All my humble opinion of course, I wish you the best of luck. -Mitch