This is one of the not-so-stomped boxes running PostgreSQL -- I've never
restarted PostgreSQL on it since it was installed.
12:03pm up 122 days, 7:54, 1 user, load average: 0.08, 0.11, 0.09
I had some index corruption problems in 6.5.3 but since 7.0.X I haven't
heard so much as a peep from any PostgreSQL backend. It's superbly stable on
all my machines..
Damn good work guys.
----- Original Message -----
From: "The Hermit Hacker" <scrappy(at)hub(dot)org>
To: "Hannu Krosing" <hannu(at)tm(dot)ee>
Cc: "xuyifeng" <jamexu(at)telekbird(dot)com(dot)cn>; <pgsql-hackers(at)postgresql(dot)org>;
"Don Baccus" <dhogaza(at)pacifier(dot)com>
Sent: Tuesday, November 28, 2000 8:53 AM
Subject: Re: [HACKERS] beta testing version
> On Tue, 28 Nov 2000, Hannu Krosing wrote:
> > xuyifeng wrote:
> > >
> > I just noticed this conversation so I have not followed all of it,
> > but you seem to have strange priorities
> > > I just want PG can be improved quickly, for me crash recover is very
> > Crash avoidance is usually much more urgent, at least on production
> > servers.
> Good call, but I kinda jumped to the conclusion that since PgSQL itself
> isn't that crash prone, its his OS or his hardware that was the problem :0
In response to
pgsql-hackers by date
|Next:||From: Joel Burton||Date: 2000-11-28 18:14:21|
|Subject: Re: Warning: Don't delete those /tmp/.PGSQL.* files |
|Previous:||From: Mitch Vincent||Date: 2000-11-28 18:07:45|
|Subject: Re: Please advise features in 7.1 (SUMMARY)|