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

From Robert Treat
Subject Re: Upcoming PG re-releases
Date
Msg-id 200512101850.41863.xzilla@users.sourceforge.net
Whole thread Raw
In response to Re: Upcoming PG re-releases  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: Upcoming PG re-releases
List pgsql-hackers
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: Simon Riggs
Date:
Subject: Re: Log of CREATE USER statement
Next
From: "Qingqing Zhou"
Date:
Subject: Re: Warm-cache prefetching