Re: [HACKERS] Shared memory corruption?

From: "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom I Helbekkmo <tih(at)Hamartun(dot)Priv(dot)NO>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Shared memory corruption?
Date: 1998-02-19 08:02:37
Message-ID: 34EBE71D.AE2C3785@sable.krasnoyarsk.su
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Meskes, Michael 1998-02-19 08:51:25 RE: New ecgp code problem.
Previous Message Oliver Elphick 1998-02-19 08:02:35 Status of glibc2 problems