Re: HOT and INSERT/DELETE
| От | Pavan Deolasee |
|---|---|
| Тема | Re: HOT and INSERT/DELETE |
| Дата | |
| Msg-id | 2e78013d0708082313m5496128vb044870fe7cd4f4@mail.gmail.com обсуждение исходный текст |
| Ответ на | HOT and INSERT/DELETE (Bruce Momjian <bruce@momjian.us>) |
| Ответы |
Re: HOT and INSERT/DELETE
|
| Список | pgsql-hackers |
On 8/9/07, Bruce Momjian <bruce@momjian.us> wrote:
As the patch stands today, we don't take any pains to update the
FSM information after pruning and defraging the page. So FSM would
not consider the page for either INSERT or COLD UPDATE. Of course,
the page can still be used for INSERT if relation->rd_targetblock is
somehow set to this page.
OTOH UPDATE will always reuse the dead space of either expired
updated rows or deleted rows or even aborted rows.
I was wondering about HOT behavior.
Will an INSERT reuse rows no longer visible caused by an UPDATE or
DELETE, or if an UPDATE will reuse rows expired by an invisible DELETE?
It seems both of these would be possible and useful.
As the patch stands today, we don't take any pains to update the
FSM information after pruning and defraging the page. So FSM would
not consider the page for either INSERT or COLD UPDATE. Of course,
the page can still be used for INSERT if relation->rd_targetblock is
somehow set to this page.
updated rows or deleted rows or even aborted rows.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: