Pretty much most people have heard of the **AA tactics against file sharers, but this time the RIAA appears to have gotten it so horribly wrong it’s just funny.
According to this article they have filed suit against a family that don’t even own a computer. How many more of these bogus extortion attempts will it take for the US legislators to sit up and take notice of the shit that these organisations are getting away with?
Perhaps my heading is a little more sensationalist then the one that I just saw on news.com.au but at least I know from the 2 line story summary that my heading would fit.
As can be clearly seen from the summary - the victim of a bikie related shooting in Sydney got up after being shot and killed and escaped from the scene in a Taxi.
Two things are obvious from this brief summary
I’m migrating a database from a postgres 7.4 server to a 8.1 server and hit a small issue with the import of the dumpfile. I’m in the middle of testing the migration at the moment and the complaint coming back from the import was about invalid UTF-8 characters in the input file. A quick google and the first link was to a page on the PostgreSQL site with the following snippet:
Some users are having problems loading UTF-8 data into 8.1.X. This is because previous versions allowed invalid UTF-8 byte sequences to be entered into the database, and this release properly accepts only valid UTF-8 sequences. One way to correct a dumpfile is to run the command iconv -c -f UTF-8 -t UTF-8 -o cleanfile.sql dumpfile.sql. The -c option removes invalid character sequences. A diff of the two files will show the sequences that are invalid. iconv reads the entire input file into memory so it might be necessary to use split to break up the dump into multiple smaller files for processing.
It works :) I had no doubt, but it is good to know that it has solved this problem.
Now my only problem is to work out why there are invalid characters in the database in the first place. But that can wait for another day. I’m off to bed!