TSearch2 performance issue?

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: TSearch2 performance issue?
Date: 2005-03-31 03:57:29
Message-ID: 424B7529.3030807@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I see this in my PQA analyzed PostgreSQL log:

######## Slowest queries
select dict_init, dict_initoption, dict_lexize from pg_ts_dict where oid
= $1

It's my number one slowest query apparently!

Can that lookup perhaps be cached in some way?

I notice that there is no unique index on the oid column, but that
shouldn't matter for performance since there are only like 6 rows in
that table.

Also, will this work with default_with_oids = false? (When the schema
is initialised.)

Chris

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-03-31 04:37:23 Re: Hash vs. HashJoin nodes
Previous Message Neil Conway 2005-03-31 03:57:01 Hash vs. HashJoin nodes