X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1080B5280B for ; Sat, 4 Jun 2005 08:40:37 -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 19745-09 for ; Sat, 4 Jun 2005 11:40:28 +0000 (GMT) Received: from viper.eo.pl (viper.eo.pl [217.17.46.133]) by svr1.postgresql.org (Postfix) with ESMTP id 350C35284B for ; Sat, 4 Jun 2005 08:40:27 -0300 (ADT) Received: from xxx.hq.eo.pl ([192.168.20.129] helo=localhost.localdomain) by viper with esmtpsa (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1DeX0r-0000Am-7j; Sat, 04 Jun 2005 13:40:29 +0200 Received: from depesz by localhost.localdomain with local (Exim 4.50) id 1DeX0p-0005Xw-A5; Sat, 04 Jun 2005 13:40:23 +0200 Date: Sat, 4 Jun 2005 13:40:23 +0200 From: hubert lubaczewski To: Christopher Kings-Lynne Cc: pgsql-performance@postgresql.org Subject: Re: strategies for optimizing read on rather large tables Message-ID: <20050604114023.GA21031@eo.pl> Reply-To: hubert.lubaczewski@eo.pl References: <20050604081742.GA29123@eo.pl> <42A18DBD.5090904@familyhealth.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <42A18DBD.5090904@familyhealth.com.au> X-info-en-1: this message *may* reflect my personal opinion. it is *not* X-info-en-2: intended to reflect those of my employer, or anyone else. X-info-pl-1: wszelkie opinie =?iso-8859-2?Q?wyra=BFone_?= =?iso-8859-2?Q?w_tym_li=B6cie_prezentuj=B1_wy=B3=B1cznie_pogl=B1dy?= X-info-pl-2: autora listu. opinie =?iso-8859-2?Q?te_?= =?iso-8859-2?Q?w_=BFadnym__razie_nie__wyra=BFaj=B1__pogl=B1d=F3w?= X-info-pl-3: pracodawcy autora =?iso-8859-2?Q?listu_?= =?iso-8859-2?Q?_ani__innych__zwi=B1zanych__z__nim__os=F3b=2E?= User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200506/88 X-Sequence-Number: 12726 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 04, 2005 at 07:17:17PM +0800, Christopher Kings-Lynne wrote: > Without reading too hard, I suggest having a quick look at contrib/ltree= =20 > module in the PostgreSQL distribution. It may or may not help you. acr_cache doesn't care about trees. and - since i have acr_cache - i dont have to worry about trees when selecting from acr_cache. ltree - is known to me. yet i decided not to use it to have the ability to move to another database engines without rewriting something that is havily used. depesz --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCoZMn5ZmPxbV4/n4RAqV5AJ417egSNTB1V4Mvi2z/XH0CEJjR+wCghJUA OzXPY/OE8JAswORgoM5BAWo= =J9cq -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+--