Re: strategies for optimizing read on rather large tables

From: hubert lubaczewski <hubert(dot)lubaczewski(at)eo(dot)pl>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: strategies for optimizing read on rather large tables
Date: 2005-06-04 11:40:23
Message-ID: 20050604114023.GA21031@eo.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message hubert lubaczewski 2005-06-04 11:41:32 Re: strategies for optimizing read on rather large tables
Previous Message PFC 2005-06-04 11:18:04 Re: strategies for optimizing read on rather large tables