Re: [HACKERS] UPDATE performance degradation (6.5.1)

Поиск
Список
Период
Сортировка
От Zeugswetter Andreas IZ5
Тема Re: [HACKERS] UPDATE performance degradation (6.5.1)
Дата
Msg-id 219F68D65015D011A8E000006F8590C60339E091@sdexcsrv1.f000.d0188.sd.spardat.at
обсуждение исходный текст
Ответы Re: [HACKERS] UPDATE performance degradation (6.5.1)  (Oleg Bartunov <oleg@sai.msu.su>)
Список 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 по дате отправления:

Предыдущее
От: Oleg Bartunov
Дата:
Сообщение: Re: [HACKERS] UPDATE performance degradation (6.5.1)
Следующее
От: wieck@debis.com (Jan Wieck)
Дата:
Сообщение: [HACKERS] Arbitrary tuple size