RE: Berkeley DB... - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject RE: Berkeley DB...
Date
Msg-id 000501bfc929$952475e0$2801007e@tpf.co.jp
Whole thread Raw
In response to RE: Berkeley DB...  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
List pgsql-hackers
> -----Original Message-----
> From: Mikheev, Vadim [mailto:vmikheev@SECTORBASE.COM]
> 
> > > Well, I've dropped index but INSERTs still take 70 sec and 
> > > COPY just 1sec -:(((
> > >
> > 
> > Did you run vacuum after dropping indexes ?
> > Because DROP INDEX doesn't update relhasindex of pg_class,
> > planner/executer may still look up pg_index.
> 
> Actually, I dropped and re-created table without indices...
>

Oops,aren't you testing in 6.5.3 ?
ExecOpenIndices() always refers to pg_index in 6.5.x.
Currently it doesn't refer to pg_index if relhasindex is
false. 

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp 


pgsql-hackers by date:

Previous
From: Alfred Perlstein
Date:
Subject: Re: but i _really can't_ insert a duplicate key!
Next
From: Tom Lane
Date:
Subject: Re: Proposed cleanup of generated header files