X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id DA12CD1B519 for ; Thu, 1 Jul 2004 18:17:18 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 89285-05 for ; Thu, 1 Jul 2004 21:17:18 +0000 (GMT) Received: from mpls-qmqp-03.inet.qwest.net (mpls-qmqp-03.inet.qwest.net [63.231.195.114]) by svr1.postgresql.org (Postfix) with SMTP id 2D71ED1B4F9 for ; Thu, 1 Jul 2004 18:17:15 -0300 (ADT) Received: (qmail 39702 invoked by uid 0); 1 Jul 2004 20:47:51 -0000 Received: from mpls-pop-02.inet.qwest.net (63.231.195.2) by mpls-qmqp-03.inet.qwest.net with QMQP; 1 Jul 2004 20:47:51 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-02.inet.qwest.net with SMTP; 1 Jul 2004 21:17:17 -0000 Date: Thu, 01 Jul 2004 15:18:14 -0600 Message-Id: <1088716694.14882.10.camel@localhost.localdomain> From: "Scott Marlowe" To: "Vincent van der Locht" Cc: pgsql-admin@postgresql.org Subject: Re: diskspace bigger after a vacuum In-Reply-To: <40E2B81F.2090105@vanderlocht.com> References: <40E2B81F.2090105@vanderlocht.com> Content-Type: text/plain Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200407/19 X-Sequence-Number: 14087 On Wed, 2004-06-30 at 06:54, Vincent van der Locht wrote: > Hi, > > I have a question, I wnat to use a postgresql database in a embedded > appliance, and thus want to keep the database as small as possible. > I'd noticed that de diskspace only grows when i do an VACUUM; or a > ./vacuumdb. Can this be explained why this is? or why this can be? > > i use postgresql 7.4.2 and run on fedora core 1. I'd look at firebirdSQL for this kind of work. It has a naturally smaller footprint, and can run, if I remember correctly, as a shared lib right underneath your application. Not that you can't slim down postgresql to fit on a smaller memory card etc... but it's just not really built for this kind of application.