[PERFORM] restoring to wrong encoding db

I was just copying a database that was in UNICODE encoding into a new db for some testing. I hand't realized it was UNICODE and when it hit some funky chinese data (from some spam that came in...) it errored out with a string too long for a varchar(255). The dump was created on PG 7.4.3 with "pg_

Re: [PERFORM] fsync vs open_sync

> > There is also the fact that NTFS is a very slow filesystem, and > > Linux is > > a lot better than Windows for everything disk, caching and IO related. > Try > > to copy some files in NTFS and in ReiserFS... > > I'm not so sure I would agree with such a blanket generalization. I find > NT

Re: [PERFORM] fsync vs open_sync

>There is also the fact that NTFS is a very slow filesystem, and > Linux is > a lot better than Windows for everything disk, caching and IO related. Try > to copy some files in NTFS and in ReiserFS... I'm not so sure I would agree with such a blanket generalization. I find NTFS to be very fa