Thread

  1. PostgreSQL's stability,

    Rostislav Matl <xmatl@informatics.muni.cz> — 1998-08-23T13:25:29Z

    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...
    Thanks.
    
    +-----------------------------------------------------------------------------+
    |  ROSTISLAV MATL, student of Masaryk University - Faculty of Informatics     |
    |  e-mail: xmatl@fi.muni.cz      WWW: http://www.fi.muni.cz/~xmatl/index.html | 
    |  ICQ#: 17058749                                                             |
    +-----------------------------------------------------------------------------+
    
    
  2. Re: [GENERAL] PostgreSQL's stability,

    Marc G. Fournier <scrappy@hub.org> — 1998-08-23T16:15:00Z

    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 @ hub.org 
    primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 
    
    
    
  3. Re: [GENERAL] PostgreSQL's stability,

    Christopher S. Weimann <cweimann@wallnet.com> — 1998-08-23T16:36:44Z

    On Sun, Aug 23, 1998 at 03:25:29PM +0200, 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...
    > Thanks.
    
    And MySql has/had a bug where telnetting to its port would prevent
    anyone else from accessing the server.  Everything has problems
    and they typically get fixed.  
    
    It doesn't surprise me that MySql lists that and doesn't give version 
    numbers or any justification.
    
    -- 
    ------------------------------------------------------------
    Christopher Weimann SysAdmin          	Wall Internet LLC. 
    Email: cweimann@wallnet.com           	PO Box 255
    Web: http://www.wallnet.com/~cweimann 	Manasquan NJ, 08736
    					732-223-1777
    ------------------------------------------------------------