| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Mike Mascari <mascarm(at)mascari(dot)com>, Matthias Urlichs <smurf(at)noris(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | RE: Berkeley DB... |
| Date: | 2000-05-26 18:32:20 |
| Message-ID: | 8F4C99C66D04D4118F580090272A7A23018C09@SECTORBASE1 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> We might have part of the story in the recently noticed fact that
> each insert/update query begins by doing a seqscan of pg_index.
>
> I have done profiles of INSERT in the past and not found any really
> spectacular bottlenecks (but I was looking at a test table with no
> indexes, so I failed to see the pg_index problem :-(). Last time
> I did it, I had these top profile entries for inserting 100,000 rows
> of 30 columns apiece:
Well, I've dropped index but INSERTs still take 70 sec and
COPY just 1sec -:(((
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Mascari | 2000-05-26 18:33:44 | Re: SPI & file locations |
| Previous Message | Joseph Shraibman | 2000-05-26 18:13:35 | Re: aliases break my query |