Re: [GENERAL] PostgreSQL's stability,

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Rostislav Matl <xmatl(at)informatics(dot)muni(dot)cz>
Cc: pgsql-general(at)postgreSQL(dot)org
Subject: Re: [GENERAL] PostgreSQL's stability,
Date: 1998-08-23 16:15:00
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-general

On Sun, 23 Aug 1998, Rostislav Matl wrote:

> Hi,
> Browsing through MySQL pages I've found crashme tests including
> note about PostgreSQL that "Anybody with access to database
> can get it down". It's that true ? I've not mentioned such
> behaviour...

There have been, in the past, several bugs that resulted in
corruption of the shared memory error that all postgres processes use.
The result of that corruption was that all the backends would either die
out, or require the superuser to kill them off and restart them.

As we have 'evolved', and those bugs are reported, they have been
addressed, and the likelihood of that happening in current releases has
dropped dramatically.

The more ppl that have access to the server, the better the chance
of it happening, since you have better odds that someone will happen to
trigger it.

If this is a large concern, though, what you can do is setup a
'server' for each client/user wishing to use it, so that they have their
own virtual area to work in, so that one person doesn't affect another.
It uses up more resources that way, but if you are more concerned with one
client not affecting another, and not with resources, then that would be a
safer way to go...

Marc G. Fournier
Systems Administrator @
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Christopher S. Weimann 1998-08-23 16:36:44 Re: [GENERAL] PostgreSQL's stability,
Previous Message Rostislav Matl 1998-08-23 13:25:29 PostgreSQL's stability,