RE: strange behaviour (bug)
От | Mikheev, Vadim |
---|---|
Тема | RE: strange behaviour (bug) |
Дата | |
Msg-id | 8F4C99C66D04D4118F580090272A7A23018CBA@SECTORBASE1 обсуждение исходный текст |
Ответ на | strange behaviour (bug) (Kovacs Zoltan <kovacsz@pc10.radnoti-szeged.sulinet.hu>) |
Ответы |
RE: strange behaviour (bug)
|
Список | pgsql-hackers |
> Probably WAL would solve this phenomenon by rolling > back the content of disc and shared buffer in reality. > However if 7.0.x would be released we had better change > bufmgr IMHO. I'm going to handle btree split but currently there is no way to rollback it - we unlock splitted pages after parent is locked and concurrent backend may update one/both of siblings before we get our locks back. We have to continue with split or could leave parent unchanged and handle "my bits moved..." (ie continue split in another xaction if we found no parent for a page) ... or we could hold locks on all splitted pages till some parent updated without split, but I wouldn't do this. Vadim
В списке pgsql-hackers по дате отправления: