| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Michal Szymanski <szymanskim(at)datera(dot)pl> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Big problem with sql update operation |
| Date: | 2007-05-25 22:38:28 |
| Message-ID: | 20070525223828.GE24789@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Michal Szymanski wrote:
> Tom Lane wrote:
> >(For the record, the reason you see nonlinear degradation is the
> >accumulation of tentatively-dead versions of the row, each of which has
> >to be rechecked by each later update.)
> >
> There is another strange thing. We have two versions of our test
> environment one with production DB copy and second genereated with
> minimal data set and it is odd that update presented above on copy of
> production is executing 170ms but on small DB it executing 6s !!!!
How are you vacuuming the tables?
--
Alvaro Herrera http://www.advogato.org/person/alvherre
"El conflicto es el camino real hacia la unión"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-05-25 23:47:00 | Re: Adding disks/xlog & index |
| Previous Message | Michal Szymanski | 2007-05-25 22:27:02 | Re: Big problem with sql update operation |