| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit |
| Date: | 2008-03-10 15:10:00 |
| Message-ID: | 47D54F48.2090904@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches pgsql-performance |
Tom Lane wrote:
> Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
>
>> It seems to happen with every statement run in the same transaction as,
>> and after, the procedure with all the subtransactions. As soon as a
>> COMMIT is executed, operations return to normal speed.
>>
>
> Ah. I misread your post as saying that it happened only once.
No worries - it's best to be sure.
Thanks for looking into it.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-10 15:10:55 | Re: [PATCHES] Include Lists for Text Search |
| Previous Message | Heikki Linnakangas | 2008-03-10 15:03:14 | Re: Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-03-10 15:16:08 | Re: count * performance issue |
| Previous Message | Heikki Linnakangas | 2008-03-10 15:03:14 | Re: Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit |