Re: [HACKERS] Shared memory corruption?

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: vadim(at)sable(dot)krasnoyarsk(dot)su (Vadim B(dot) Mikheev)
Cc: tih(at)Hamartun(dot)Priv(dot)NO, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Shared memory corruption?
Date: 1998-02-19 14:24:36
Message-ID: 199802191424.JAA17951@candle.pha.pa.us
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.

I always have asserts on.

--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1998-02-19 14:31:50 Re: pg_user permissions problem (Was: Re: [HACKERS] RE: New ecgp code problem.)
Previous Message The Hermit Hacker 1998-02-19 14:14:36 Re: [HACKERS] Solution to the pg_user passwd problem !?? (c)