Re: [HACKERS] UPDATE performance degradation (6.5.1)

From: Zeugswetter Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at>
To: "'Oleg Bartunov'" <oleg(at)sai(dot)msu(dot)su>
Cc: "'hackers(at)postgresql(dot)org'" <hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] UPDATE performance degradation (6.5.1)
Date: 1999-07-27 14:57:06
Message-ID: 219F68D65015D011A8E000006F8590C60339E091@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> This is for table with one row after a lot of updates.
> Too much. vacuum analyze this table was a good medicine !
> Is this a design problem ?
>
In PostgreSQL an update always adds a new row to the table.
The old rows get eliminated by vacuum that is the whole business of vacuum.
There has been some discussion for implementing row reuse,
but that is a major task.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-07-27 14:57:36 Re: [HACKERS] UPDATE performance degradation (6.5.1)
Previous Message Oleg Bartunov 1999-07-27 14:52:56 Re: [HACKERS] UPDATE performance degradation (6.5.1)