Re: Phantom Command ID

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: Phantom Command ID
Дата
Msg-id 45125F6E.2010108@enterprisedb.com
обсуждение исходный текст
Ответ на Re: Phantom Command ID  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Phantom Command ID  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Tom Lane wrote:
> Heikki Linnakangas <heikki@enterprisedb.com> writes:
>   
>> A big question is, do we need to implement spilling to disk?
>>     
>
> My thought is no, at least not in the first cut ... this is something
> that can be added later if it proves critical, and right at the moment
> my guess is that it never will.  The data structure design sounds fine.
>   

I thought so too.

We could also limit the size of the hash table, which takes up most of 
the memory, and only keep the latest phantom cids there. Presumably, if 
current command id is 1000, you're not likely to set cmax to 500 on any 
tuple in that transaction anymore.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Csaba Nagy
Дата:
Сообщение: Re: [PATCHES] Incrementally Updated Backup
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: Phantom Command ID