vacuum causes it because the system does not use indexes until the
vacuum is performed.

Good news and bad news.  The good news is that it works perfectly on the
current source tree because we have made some improvements since 6.3. 
Bad news is that the 6.4 release is not in beta until the end of the
month.

Hope you can wait until then.  If you want to try the developement tree
just for curiosity, it is on our ftp site at ftp.postgresql.org.


> Hi,
> 
> > What PostgreSQL version are you running?
> Sorry. It's 6.3.2 and running on IRIX6.4
> 
> It seems, that this error has something to do with vacuum. I've created a new
> database and did the following:
> 
> ------------------------------------------------------------------
> try_db=> CREATE TABLE dom_prot (
> try_db-> domain text not null,
> try_db-> protein text not null,
> try_db-> start int4 not null,
> try_db-> ende int4 not null,
> try_db-> score int4,
> try_db-> e_value float8,
> try_db-> p_value char16,
> try_db-> primary key (domain, protein, start, ende));
> NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index dom_prot_pkey for
> table dom_prot
> CREATE
> try_db=> copy dom_prot from '/tmp/load_it';
> COPY


-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

Tue, 11 Aug 1998 11:02:31 -0400 (EDT)
Bruce Momjian <maillist@candle.pha.pa.us>
Re: [GENERAL] ExecInitIndexScan ERROR?