X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 9B83D9DCBA6 for ; Sat, 3 Dec 2005 11:46:19 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 50655-05 for ; Sat, 3 Dec 2005 11:46:14 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mailbox.samurai.com (mailbox.samurai.com [205.207.28.82]) by postgresql.org (Postfix) with ESMTP id 2533A9DCB93 for ; Sat, 3 Dec 2005 11:46:17 -0400 (AST) Received: from localhost (mailbox.samurai.com [205.207.28.82]) by mailbox.samurai.com (Postfix) with ESMTP id 0A2A12397A9; Sat, 3 Dec 2005 10:46:22 -0500 (EST) Received: from mailbox.samurai.com ([205.207.28.82]) by localhost (mailbox.samurai.com [205.207.28.82]) (amavisd-new, port 10024) with LMTP id 67206-01-4; Sat, 3 Dec 2005 10:46:20 -0500 (EST) Received: from [192.168.1.104] (d226-86-55.home.cgocable.net [24.226.86.55]) by mailbox.samurai.com (Postfix) with ESMTP id 8D3C2239773; Sat, 3 Dec 2005 10:46:20 -0500 (EST) Subject: Re: Upcoming PG re-releases From: Neil Conway To: Tom Lane Cc: pgsql-hackers@postgreSQL.org In-Reply-To: <26656.1133366185@sss.pgh.pa.us> References: <26656.1133366185@sss.pgh.pa.us> Content-Type: text/plain Date: Sat, 03 Dec 2005 10:56:11 -0500 Message-Id: <1133625371.9297.3.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mailbox.samurai.com X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200512/140 X-Sequence-Number: 76988 On Wed, 2005-11-30 at 10:56 -0500, Tom Lane wrote: > It's been about a month since 8.1.0 was released, and we've found about > the usual number of bugs for a new release, so it seems like it's time > for 8.1.1. I think one fix that should be made in time for 8.1.1 is adding a note to the "version migration" section of the 8.1 release notes describing the "invalid UTF-8 byte sequence" problems that some people have run into when upgrading from prior versions. I'm not familiar enough with the problem or its remedies to add the note myself, though. -Neil