From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | "Differentiated Software Solutions Pvt(dot) Ltd(dot)" <diffs(at)vsnl(dot)com> |
Cc: | pgsql-general(at)postgreSQL(dot)org, Kimi <kimi(at)intercept(dot)co(dot)in> |
Subject: | Re: [GENERAL] Postgres instability : AN APPEAL |
Date: | 1999-12-15 04:40:46 |
Message-ID: | Pine.BSF.4.21.9912150039010.651-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Since you haven't provided much information, lets' start with:
what version of PostgreSQL?
what operating system?
and we can work from that... :)
On Wed, 15 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:
> Hi,
>
> I have unfortunately programmed a mission critical application in postgres
> without doing full load testing.
> Now I'm getting lots of messages when I start stressing it.
> Typical messages include --- Spinlock error, ReleaseLRU no files found etc.,
> Last couple of days I'm battling by switching on the pgoptions. They don't
> seem to help... because I can't correlate which message is coming from which
> process or session or SQL.
> I have posted a detailed message on this error last week. Nobody responded.
>
> THIS IS AN APPEAL. If any of you has experience in handling postgres locking
> and instabilities.... CAN YOU PLEASE WRITE TO ME. I'm desperate to talk to
> somebody who can understand my problems and give me some intelligent
> suggestions.
>
> Thanks in Advance,
>
> Murali
>
>
> Differentiated Software Solutions Pvt. Ltd.,
> 176, Gr. Floor, 6th Main
> 2nd Block RT Nagar
> Bangalore - 560 032
> India
> Ph: 91 80 3431470
>
>
>
> ************
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Bob Pfeiff | 1999-12-15 04:44:02 | Re: Memory bug |
Previous Message | Differentiated Software Solutions Pvt. Ltd. | 1999-12-15 03:56:02 | Postgres restart problems |