Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 09B819FB661 for ; Wed, 11 Jul 2007 09:49:50 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 82981-10 for ; Wed, 11 Jul 2007 09:49:40 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (unknown [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 6E0C89FB466 for ; Wed, 11 Jul 2007 09:49:46 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-221-218-82.bk12-dsl.surnet.cl [201.221.218.82]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l6BCnbeK021124; Wed, 11 Jul 2007 05:49:39 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 4EA1C47C44; Wed, 11 Jul 2007 08:49:37 -0400 (CLT) Date: Wed, 11 Jul 2007 08:49:37 -0400 From: Alvaro Herrera To: Tom Lane Cc: Ray Stell , pgsql-admin@postgresql.org Subject: Re: 8.2.4 patches? Message-ID: <20070711124937.GA3294@alvh.no-ip.org> References: <20070710203232.GA18997@cns.vt.edu> <20070710210010.GB19521@alvh.no-ip.org> <11906.1184110787@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11906.1184110787@sss.pgh.pa.us> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV 0.90.3/3634/Tue Jul 10 18:14:01 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 11 Jul 2007 05:49:44 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/100 X-Sequence-Number: 26081 Tom Lane wrote: > Alvaro Herrera writes: > > Ray Stell wrote: > >> Are there critical security or performance patches that should be > >> applied to 824 and how could I have determined this without this post? > > > The changelog after 8.2.4 is below. I don't think there's a way to get > > this easily, short of having a copy of the CVS repository. > > The other way to check the change history is to troll the > pgsql-committers archives > http://archives.postgresql.org/pgsql-committers/ > although certainly cvs2cl output is a lot easier to scan. > > My $0.02: if you really want the latest and greatest, the nightly > snapshot tarball of the current stable branch would be the thing to > grab, rather than fooling with individual patches. Hmm, do we include the cvs2cl-generated ChangeLog in the tarballs? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support