Re: BUG #1502: hash_seq_search might return removed entry
От
Thomas Hallgren
Тема
Re: BUG #1502: hash_seq_search might return removed entry
Дата
Msg-id
thhal-0fpb9AkUNxycEfTL8c+al9q2zmIUknD@mailblocks.com
Ответ на
Список
Дерево обсуждения
BUG #1502: hash_seq_search might return removed entry "Thomas" <thhal@mailblocks.com>
Re: BUG #1502: hash_seq_search might return removed entry Tom Lane <tgl@sss.pgh.pa.us>
Re: BUG #1502: hash_seq_search might return removed entry Thomas Hallgren <thhal@mailblocks.com>
Re: BUG #1502: hash_seq_search might return removed entry Bruce Momjian <pgman@candle.pha.pa.us>
Re: BUG #1502: hash_seq_search might return removed entry Thomas Hallgren <thhal@mailblocks.com>
Re: BUG #1502: hash_seq_search might return removed entry Tom Lane <tgl@sss.pgh.pa.us>
Re: BUG #1502: hash_seq_search might return removed entry Thomas Hallgren <thhal@mailblocks.com>
Tom Lane wrote: >Thomas Hallgren writes: > > >>Would such a patch be accepted? >> >> > >Seems like a brute-force solution. I'd look first at whether >AtCommit_Portals could just restart its hashtable scan after >each deletion; if that seems too inefficient, modify the hash >table entries themselves to carry a "portal already deleted" >flag. > > Yes, a static flag indicating that a deletion has occured will work fine since all portals that has not been perused but not dropped now has an InvalidSubTransactionId. I'll do it that way then. Regards, Thomas Hallgren
В списке pgsql-bugs по дате отправления
От: Barry Brown
Дата: