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-13 02:29:37
Message-ID: 199802130229.VAA01001@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'll try to deal with this in the next week.
> I'm going to update CVS with subselect support right now
> and I'll try to fix bugs after this.

Great. Thanks.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vadim B. Mikheev 1998-02-13 02:30:18 Re: [HACKERS] Shared memory corruption?
Previous Message Dr. Huaimin Wang 1998-02-13 02:05:44