[rt-users] 3.4.2 to 4.x

[Jeff Blaine]

On 12/28/2011 9:50 AM, Darin Perusich wrote:
> Hi Jeff,
>
> I did an upgrade from mysql to postgres a few month back and it went
> very smoothly. I used the rt-mysql2pg script available at
> http://wiki-archive.bestpractical.com/view/rt-mysql2pg to convert the
> data which performed seamlessly.

Hi Darin,

Oh jeez.  I wish I'd known about that earlier!

It's working fine so far.  Chugging along.

> I have a bunch of notes I can share which might be helpful, I ran into a
> few issues performing the update because of AssetTracker. Ping me
> off-list and I'll share them.
>
> On 12/28/2011 09:30 AM, Jeff Blaine wrote:
>> The RT 3.4 to RT 4.0.4 upgrade went fine.
>>
>> Now with our data in MySQL 5.1.x, instead of the old
>> MySQL 4.1, and our new instance not in production yet,
>> we want to migrate to PostgreSQL 8.4.9, largely in
>> order to get performant full-text searching without
>> doing something hackish with MySQL and Sphinx nonsense.
>>
>> That task, however, is turning out to be a nightmare.
>> The gory details are at the link below, but the short
>> story is that PostgreSQL does not like some of the
>> bytes (mostly when trying to INSERT into Attachments).
>>
>> Cleaning the dump file of all non-ASCII characters,
>> then trying the data load again, bought me nothing (!!??).
>>
>> http://dba.stackexchange.com/questions/9792/no-nulls-yet-invalid-byte-sequence-for-encoding-utf8-0x00
>>
>>
>> If anyone has any advice, please share!
>> --------
>> RT Training Sessions (http://bestpractical.com/services/training.html)
>> * Boston  March 5&  6, 2012
>