Thread

1. Re: [HACKERS] backend crashing on NetBSD 1.3.2/i386

   Tom Lane <tgl@sss.pgh.pa.us> — 1998-11-01T17:23:07Z

   Brook Milligan <brook@trillium.NMSU.Edu> writes:
   > Until earlier this week, the various snapshots have been working fine
   > on my system, NetBSD 1.3.2/i386.  As of a couple of days ago the
   > backend started to crash.
   
   When did this start, exactly?
   
   > I hoped this was a temporary glitch with
   > recent patches which would disappear in a day or so as other stuff got
   > sorted out.  Nothing seems to have changed, though, over the last
   > several days, and connections fail with the backend crashing.
   
   A reproducible crash at startup ought to be pretty easy to nail down.
   Does it produce a corefile?  If so fire up gdb and get a backtrace so
   we can see where the crash occurs.  (The trace would give more info if
   you compiled with -g, but even without it would be helpful.)
   
   One thing that comes to mind quickly is that some of the changes this
   week required an initdb to be fully effective.  If you forgot the initdb
   maybe a crash at startup would result; I'm not sure.
   
   			regards, tom lane
   
   

2. Re: [HACKERS] backend crashing on NetBSD 1.3.2/i386

   Tom Ivar Helbekkmo <tih@nhh.no> — 1998-11-01T18:18:10Z

   I'm running an installation on NetBSD/i386 1.3.2 that I upgraded
   (using 'cvs update') just a couple of hours ago, and it's behaving
   just fine.  I've loaded a few megabytes of data into it, and done a
   bit of updating and querying, with no problems.
   
   Tom Lane <tgl@sss.pgh.pa.us> writes:
   
   > One thing that comes to mind quickly is that some of the changes this
   > week required an initdb to be fully effective.  If you forgot the initdb
   > maybe a crash at startup would result; I'm not sure.
   
   That may be it.  I always use pg_dump and initdb when I update the
   systems I run a current snapshot of PostgreSQL on, just to be sure.
   
   -tih
   -- 
   Popularity is the hallmark of mediocrity.  --Niles Crane, "Frasier"
   
   

3. Re: [HACKERS] backend crashing on NetBSD 1.3.2/i386

   Brook Milligan <brook@trillium.nmsu.edu> — 1998-11-01T22:28:38Z

      > Until earlier this week, the various snapshots have been working fine
      > on my system, NetBSD 1.3.2/i386.  As of a couple of days ago the
      > backend started to crash.
   
      When did this start, exactly?
   
   Sometime between Monday and Thursday, but Marc just trashed the old
   BETA* files so I can't go back and check.  I did manage to catch the
   BETA3 just before it disappeared and it exhibits the problem.
   
      One thing that comes to mind quickly is that some of the changes this
      week required an initdb to be fully effective.  If you forgot the initdb
      maybe a crash at startup would result; I'm not sure.
   
   Nope.  For testing the new version I've been doing a clean install
   every time, including initdb and everything.
   
   Cheers,
   Brook
   
   

4. Re: [HACKERS] backend crashing on NetBSD 1.3.2/i386

   Brook Milligan <brook@trillium.nmsu.edu> — 1998-11-01T22:31:11Z

      I'm running an installation on NetBSD/i386 1.3.2 that I upgraded
      (using 'cvs update') just a couple of hours ago, and it's behaving
      just fine.  I've loaded a few megabytes of data into it, and done a
      bit of updating and querying, with no problems.
   
   Do you see the warnings about select() when compiling s_lock.c?
   
   Cheers,
   Brook
   
   

5. Re: [HACKERS] backend crashing on NetBSD 1.3.2/i386

   Tom Ivar Helbekkmo <tih@nhh.no> — 1998-11-02T11:37:44Z

   Brook Milligan <brook@trillium.NMSU.Edu> writes:
   
   > Do you see the warnings about select() when compiling s_lock.c?
   
   Yup.
   
   -tih
   -- 
   Popularity is the hallmark of mediocrity.  --Niles Crane, "Frasier"