X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 7303BD1B552 for ; Fri, 3 Oct 2003 16:11:12 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 86269-03 for ; Fri, 3 Oct 2003 13:10:22 -0300 (ADT) Received: from ucsns.ucs.co.za (ucs.co.za [196.23.43.2]) by svr1.postgresql.org (Postfix) with ESMTP id BACC4D1B53E for ; Fri, 3 Oct 2003 13:10:17 -0300 (ADT) Received: from ucspost.ucs.co.za (mailgw1.ucs.co.za [196.23.43.253]) by ucsns.ucs.co.za (Postfix) with ESMTP id 4EA932BDC0; Fri, 3 Oct 2003 18:10:10 +0200 (SAST) Received: from jhb.ucs.co.za (jhb.ucs.co.za [172.31.1.3]) by ucspost.ucs.co.za (Postfix) with ESMTP id 28867DA934; Fri, 3 Oct 2003 18:10:10 +0200 (SAST) Received: from svb.ucs.co.za (svb.ucs.co.za [172.31.1.148]) by jhb.ucs.co.za (Postfix) with SMTP id EB570973EA; Fri, 3 Oct 2003 18:10:09 +0200 (SAST) Date: Fri, 3 Oct 2003 18:10:02 +0200 From: Stef To: Tom Lane Cc: pgsql-performance@postgresql.org Subject: Re: Postgres low end processing. Message-Id: <20031003181002.20cc6912.svb@ucs.co.za> In-Reply-To: <24646.1065195774@sss.pgh.pa.us> References: <20031003163040.3641f39a.svb@ucs.co.za> <24646.1065195774@sss.pgh.pa.us> X-Mailer: Sylpheed version 0.9.5claws28 (GTK+ 1.2.10; i386-pc-linux-gnu) User-Agent: sillypheed-claws (anti-aliased) X-Face: LV^-*d3kQlL,6{Y:X)M~tuL#y!p.kO_Qbc!xxqhZC4s}Y]L0g)z^aiLsQGY34d|}Xp:HNm)MRsc?^?ZQ}smznF&jx|w@,a**K&QL.Dc~2~M5V`zb>hExCJDB[[o=M)e"; k-n[7tz2TY7+; *_xX's(5cUEtdw*yG-OmKm}6($zpUz8S`Nz@w X-Operating-System: sid X-X-X: _-^-_ Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Fri__3_Oct_2003_18_10_02_+0200_RUHA.E2bYB1TIrpy" X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/91 X-Sequence-Number: 3839 --Signature=_Fri__3_Oct_2003_18_10_02_+0200_RUHA.E2bYB1TIrpy Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Fri, 03 Oct 2003 11:42:54 -0400 Tom Lane wrote: => Are you sure you want Postgres, and not something smaller? BDB, => or SQL Lite, for example? I have considered various options, including BDB and SQL Lite, but alas, it will have to be postgres if it's going to be a database. Otherwise it will be back to the original idea of flat .idx files :( => "Postgres is bloatware by design: it was built to house PhD theses." => -- J. Hellerstein (who ought to know) :o) Believe me, I've been amazed since I encountered postgres v6.3.2 in '98 => But having said that ... given virtual memory and cramped configuration => settings, Postgres would certainly run in an 8M machine. Maybe "crawl" => would be a more applicable verb than "run", but you could execute it. Crawling is ok. Won't differ much from normal operation on a machine like that. Any tips on how to achieve the most diminutive vmem an conf settings? I tried to figure this out from the docs, and played around with backend/storage , but I'm not really winning. Regards Stef --Signature=_Fri__3_Oct_2003_18_10_02_+0200_RUHA.E2bYB1TIrpy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/fZ9hgDYs3UkRjZkRAugiAJ905TWfgHxYHmS4nB6kUkjLD6x6fACdF/su FBDEM07zuuSR28recUKeBSc= =GXG7 -----END PGP SIGNATURE----- --Signature=_Fri__3_Oct_2003_18_10_02_+0200_RUHA.E2bYB1TIrpy--