From: hubert lubaczewski <hubert.lubaczewski@eo.pl>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: strategies for optimizing read on rather large tables
Date: Sat, 4 Jun 2005 13:40:23 +0200
Message-ID: <20050604114023.GA21031@eo.pl> (raw)
In-Reply-To: <42A18DBD.5090904@familyhealth.com.au>
References: <20050604081742.GA29123@eo.pl>
<42A18DBD.5090904@familyhealth.com.au>
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
> 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
Attachments:
signature.asc (application/pgp-signature, 188B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: hubert.lubaczewski@eo.pl, chriskl@familyhealth.com.au
Subject: Re: strategies for optimizing read on rather large tables
In-Reply-To: <20050604114023.GA21031@eo.pl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox