Re: CVS stability

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sean Davis <sdavis2(at)mail(dot)nih(dot)gov>
Cc: Postgresql-General list <pgsql-general(at)postgresql(dot)org>
Subject: Re: CVS stability
Date: 2005-06-12 15:15:53
Message-ID: 24045.1118589353@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> writes:
> I've been noticing some very useful things that are probably already in
> CVS (return_next in pl/perl, IN/OUT parameters, and probably others).
> I don't have a "mission critical" production environment and was
> wondering how unstable a typical 8.1 CVS checkout is? I'm not talking
> about feature-freeze, but more about uptime and compilation.

CVS tip is seldom actively broken; the main downside you have to be
prepared for is that a snapshot will not be forwards or backwards
initdb-compatible. As long as you are prepared for a full dump/restore
any time you want to update, you can certainly use it for development
work.

You might consider grabbing one of the nightly snapshot tarballs instead
of pulling directly from CVS --- less setup overhead that way (in
particular you don't need any tools you wouldn't need for a regular
source build).

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jernej Kos 2005-06-12 15:53:41 Re: Postgre "idle" process using 100% CPU
Previous Message Tino Wildenhain 2005-06-12 12:32:48 Re: PostgreSQL Certification