Does anyone have time to do a binary search on cvs for the days
between known good and known bad?

If someone has a test case that is fairly easy to populate the
database and leave the script running, I can try to do the search this
weekend on an i386 box.

I would need to know the latest possible dates for last known working
kernels and the earliest possible known broken.

-Andrew

On Thu, 20 Jan 2005 19:25:01 +0000, Andreas Drewke <andreas_dr@gmx.de> wrote:
> I see, this is a problem of NetBSD 2.0 not of PostgreSQL.
> Ok the machine where these version of pgsql is stable is running NetBSD
> current!
> 
> Argh.
> 
> I choosed NetBSD 2.0 for the other machine where I have those problems because
> it is or was a production machine since I updated it. This is really bad. If
> releng would be there I could at least try to just exchange the kernel with a
> newer one.
> 
> *whining* and off
> 
> On Thursday 20 January 2005 15:26, Andreas Drewke wrote:
> > Just for your knowledge:
> >
> > This set of pgsql is working very stable.
> >
> > postgresql74-client-7.4.3nb1 PostgreSQL database client programs
> > postgresql74-server-7.4.3 PostgreSQL database server programs
> > postgresql74-docs-7.4.3 PostgreSQL database system documentation
> > postgresql74-7.4.3  Robust, next generation, object-relational DBMS
> > postgresql74-lib-7.4.3 PostgreSQL database headers and libraries
> >
> > I am curious when pgsql 8.0 will be imported into pkgsrc.
> >
> > Regards
> > Andreas
> >
> > On Thursday 20 January 2005 13:35, you wrote:
> > > Hi,
> > >
> > > On Thu, Jan 20, 2005 at 02:23:59PM +0000, Andreas Drewke wrote:
> > > > Second thing ist that the current postgresql 7.4.6 server from pkgsrc
> > > > seems to have problems too. At some point (didnt investigate it
> > > > further) it starts to eat 100% cpu and never gets out of this state
> > > > again.
> > >
> > > FYI, I'm seeing this too but with postgresql 7.3.8 (installed from
> > > pkgsrc-2004Q4).
> > >
> > >
> > >      -sk
> 
> --
> 
> www: http://drewke.net / icq:175089452
>