| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Edmund Mergl <E(dot)Mergl(at)bawue(dot)de> |
| Cc: | PostgreSQL Hackers Mailinglist <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] strange behavior of UPDATE |
| Date: | 1999-05-26 13:42:30 |
| Message-ID: | 12739.927726150@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Edmund Mergl <E(dot)Mergl(at)bawue(dot)de> writes:
>> Could you try the same queries with no indexes in place, and see what
>> the time scaling is like then? That would confirm or deny the theory
>> that it's an index-update problem.
> here they are, and yes, I double-checked them twice !
> database #rows inserts create make_sqs make_nqs
> index selects updates
> ----------------------------------------------------------------------------
> pgsql 10.000 00:24 - 00:13 00:05
> pgsql 100.000 04:01 - 00:83 00:32
> pgsql 1.000.000 39:24 - 26:36 26:52
Oh dear ... so much for my theory that index updates are to blame for
the scaling problem. Back to the drawing board ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 1999-05-26 13:48:52 | Re: [HACKERS] Help: fmgr_info: function 0: cache lookup failed |
| Previous Message | Tom Lane | 1999-05-26 13:39:12 | Re: [HACKERS] strange behavior of UPDATE |