Re: [HACKERS] Shared memory corruption? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Shared memory corruption?
Date
Msg-id 199802191424.JAA17951@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] Shared memory corruption?  ("Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>)
List 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.

I always have asserts on.

--
Bruce Momjian
maillist@candle.pha.pa.us

pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Solution to the pg_user passwd problem !?? (c)
Next
From: Bruce Momjian
Date:
Subject: Re: pg_user permissions problem (Was: Re: [HACKERS] RE: New ecgp code problem.)