| From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
| Cc: | "Mike Mascari" <mascarm(at)mascari(dot)com>, "Matthias Urlichs" <smurf(at)noris(dot)de>, <pgsql-hackers(at)postgresql(dot)org>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Hannu Krosing" <hannu(at)tm(dot)ee> |
| Subject: | RE: Berkeley DB... |
| Date: | 2000-05-29 04:51:42 |
| Message-ID: | 000501bfc929$952475e0$2801007e@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: Mikheev, Vadim [mailto:vmikheev(at)SECTORBASE(dot)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(at)tpf(dot)co(dot)jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-05-29 05:54:16 | Re: Proposed cleanup of generated header files |
| Previous Message | Alfred Perlstein | 2000-05-29 04:49:29 | Re: but i _really can't_ insert a duplicate key! |