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 CD7A89DD898 for ; Sun, 11 Dec 2005 01:30:38 -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 56112-07 for ; Sun, 11 Dec 2005 01:30:35 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by postgresql.org (Postfix) with ESMTP id 53ECC9DD880 for ; Sun, 11 Dec 2005 01:30:34 -0400 (AST) Received: from [192.168.1.101] (or-67-76-146-141.sta.sprint-hsd.net [67.76.146.141]) (authenticated bits=0) by hosting.commandprompt.com (8.13.4/8.13.4) with ESMTP id jBB5NKZV011474; Sat, 10 Dec 2005 21:23:24 -0800 Message-ID: <439BB964.30508@commandprompt.com> Date: Sat, 10 Dec 2005 21:30:12 -0800 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: Bruce Momjian CC: Robert Treat , pgsql-hackers@postgresql.org, Martijn van Oosterhout , Gregory Maxwell , Gavin Sherry , Peter Eisentraut Subject: Re: Upcoming PG re-releases References: <200512110218.jBB2I0V18560@candle.pha.pa.us> In-Reply-To: <200512110218.jBB2I0V18560@candle.pha.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (hosting.commandprompt.com [192.168.1.101]); Sat, 10 Dec 2005 21:23:28 -0800 (PST) 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/560 X-Sequence-Number: 77408 Bruce Momjian wrote: > I don't see it asked very often, and I think our 8.1 releae note > addition (plus a mention in the 8.1.1 notes) will complete this. > > Actually a "upgrade" FAQ is probably a good idea. Something that says what really happens when foo changes in 8.1 or how foo is different then 8.0. The idea that there is a practical (for those that have practical implications) resource for finding out what it really means that the UTF-8 stuff changed . Joshua D. Drake > --------------------------------------------------------------------------- > > Robert Treat wrote: > >> Was thinking if someone could summarize this all it would make a really good >> FAQ entry. >> >> Robert Treat >> >> On Friday 09 December 2005 13:28, Martijn van Oosterhout wrote: >> >>> On Fri, Dec 09, 2005 at 12:38:21PM -0500, Bruce Momjian wrote: >>> >>>>> This means someone who is planning on upgrading to 8.1 in two months >>>>> can use this function now to weed out the bad data before the upgrade >>>>> even starts. >>>>> >>>> Oh, so you back-load it into the old database. Interesting. I assume >>>> to be useful you would have to write something that checked every column >>>> values in every table and database. >>>> >>> Umm, yeah. I was thinking about how to do that. pl/pgsql is not the >>> best language to do that in. In any case I found a bug in the version I >>> posted and also added a function that does: >>> >>> test=# select * from db_utf8_verify(); >>> tab | fld | location >>> ------+-----+---------- >>> tbl1 | foo | (12,3) >>> (1 row) >>> >>> It gives the table, field and ctid of any values that failed. It skips >>> pg_catalog. It's also *really* slow for long strings. Just executing it >>> on the pg_rewrite in the default installation takes forever. If someone >>> really wanted this for a large database maybe they should recode it in >>> C. >>> >>> http://svana.org/kleptog/pgsql/utf8_verify.sql >>> >>> Have a nice day, >>> >> -- >> Robert Treat >> Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL >> >> > >