Re: [HACKERS] Shared memory corruption?
От | Vadim B. Mikheev |
---|---|
Тема | Re: [HACKERS] Shared memory corruption? |
Дата | |
Msg-id | 34EBE71D.AE2C3785@sable.krasnoyarsk.su обсуждение исходный текст |
Ответ на | Re: [HACKERS] Shared memory corruption? (Bruce Momjian <maillist@candle.pha.pa.us>) |
Ответы |
Re: [HACKERS] Shared memory corruption?
|
Список | pgsql-hackers |
Bruce Momjian wrote: > > Vadim, I may need your help on this one. I can reproduce it by runinng > the regression test, and doing a shell 'while' loop that continuously > creates databases: > > while : > do > sh -c 'createdb $$' > done > > I get the errors too. I have no idea on a cause. I would hope it is > not the new deadlock code, or locking fixes I did. I think the message > comes from smgrblindwrt. Is it possible our new speedups are causing > it? I can reproduce it. Keep looking... BTW, did you compile without --enable-cassert ? (Should be ON by default in beta-s...) I got some interest assertion from BufferAlloc, without CASSERT you should get dead spinlock from there. Vadim
В списке pgsql-hackers по дате отправления: