Re: Upcoming PG re-releases - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Upcoming PG re-releases
Date
Msg-id 439BB964.30508@commandprompt.com
Whole thread Raw
In response to Re: Upcoming PG re-releases  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
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
>>
>>     
>
>   



pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: New packages built ...
Next
From: "Anjan Kumar. A."
Date:
Subject: Please Help: PostgreSQL Query Optimizer