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-13 02:30:18
Message-ID: 34E3B03A.B5E4437A@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'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.

Vadim

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Stockwell 1998-02-13 04:03:13 postgres initdb on ALPHA/Digital Unix
Previous Message Bruce Momjian 1998-02-13 02:29:37 Re: [HACKERS] Shared memory corruption?