Return-Path: owner-postman
Received: from localhost (localhost [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with SMTP id KAA21321 for postgres-dist; Thu, 3 Feb 1994 10:32:15 -0800
Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199402031832.KAA21321@nobozo.CS.Berkeley.EDU>
X-Authentication-Warning: nobozo.CS.Berkeley.EDU: Host localhost didn't use HELO protocol
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: owner-postman
Received: from liblas.byu.edu (liblas.byu.edu [128.187.11.118]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with SMTP id KAA21312 for <postgres@nobozo.CS.Berkeley.EDU>; Thu, 3 Feb 1994 10:32:13 -0800
Received: by liblas.byu.edu; id AA20531; Thu, 3 Feb 1994 11:34:38 -0700
From: Brian Holman <bkh@liblas.byu.edu>
Message-Id: <9402031834.AA20531@liblas.byu.edu>
Subject: Re: Postgres v4.2? OSF/1 Port?
To: postgres@postgres.Berkeley.EDU
Date: Thu, 3 Feb 1994 11:34:29 +119303928 (MST)
In-Reply-To: <199401290016.QAA26997@nobozo.CS.Berkeley.EDU> from "Paul M. Aoki" at Jan 28, 94 04:16:53 pm
X-Mailer: ELM [version 2.4 PL22]
Content-Type: text
Content-Length: 1779      
Resent-To: postgres-dist@postgres.Berkeley.EDU
Resent-Date: Thu, 03 Feb 94 10:32:15 -0800
Resent-XMts: smtp

Paul Aoki <aoki@postgres.berkeley.edu> writes:
> when a backend dies unexpectedly, the postmaster detaches its 
> shared resources and reinitializes from scratch.  (i don't think 
> there's any good reason to actually detach the resources before 
> reinitializing, but there it is.)  sometimes it fails to reattach 
> (it prints out a message when this happens) and terminates.
> 
> i think this was partly due to the way backends neglected to shmdt 
> (detach) when going down.  this would occasionally cause the postmaster 
> to "leak" shared resources (which couldn't be deallocated by the OS 
> because it thought a process was still attached).  i changed the 
> shared memory stuff to shmdt and i didn't see this problem anymore on
> ultrix 4.2a.  we upgraded the sequoia 2000 db server machine to ultrix 
> 4.3a and the problem seemed to go away in the old code, too -- it was
> up for about two months without this problem.
> 
> i think i sent that shmdt change to robert withrow, who was reporting 
> something similar under SVR4, to see if that solved his problem.  i 
> don't remember what his conclusion was, though.

Is the "old code" the release of 4.1 available on the ftp site?  Is the "new
code" available?  I noticed a sequoia 2000 tar file on s2k-ftp.  Does this
contain the fix and is it rightful for me to get it not having anything to
do with sequoia?
-- 
+--------------------------+-------------------------------------+
| BRIAN K. HOLMAN          | E-Mail:        brian_holman@byu.edu |
| Programmer/Analyst       | Mail:    2330 HBLL, Provo, UT 84602 |
| Library Automations      | Phone:               (801) 378-8162 |
| Brigham Young University | Fax:                 (801) 378-3221 |
+--------------------------+-------------------------------------+