Re: [HACKERS] UPDATE performance degradation (6.5.1) - Mailing list pgsql-hackers

From Zeugswetter Andreas IZ5
Subject Re: [HACKERS] UPDATE performance degradation (6.5.1)
Date
Msg-id 219F68D65015D011A8E000006F8590C60339E091@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
Responses Re: [HACKERS] UPDATE performance degradation (6.5.1)
List 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


pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: [HACKERS] UPDATE performance degradation (6.5.1)
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: [HACKERS] Arbitrary tuple size