No, the file needs to be nothing but hex value 55 throughout. The attachment I sent earlier is just that:
[EMAIL PROTECTED]:~$ hexdump 55 0000000 5555 5555 5555 5555 5555 5555 5555 5555 * 0040000 i.e. all 55s, all the time, not the ascii numbers 5 and 5, but the hex value. The actual file is ascii the letter U over and over: [EMAIL PROTECTED]:~$ head -c 100 55 UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU and so on. On Wed, Sep 24, 2008 at 12:09 PM, Carol Walter <[EMAIL PROTECTED]> wrote: > To use the hex value 0x55, do I need to enclose it in single quotes? > > Carol > > On Sep 24, 2008, at 11:44 AM, Tom Lane wrote: > >> Carol Walter <[EMAIL PROTECTED]> writes: >>> >>> Are the files that contain the hex characters supposed to contain a >>> single string and no control characters? >> >> Yes, you want 256K occurrences of the byte value 0x55 and nothing else. >> >>> I'm also wondering if, after I create the dummy files, and pg_dump >>> works, I could restore an old pg_dumpall file and then insert any >>> data that aren't there from the pg_dumps. >> >> It'd be a good idea to do as much cross-checking as you can, since >> it's highly probable that the dumped data will be at least partly wrong. >> >> No, I'm afraid updating to 8.2.latest won't get you out of this. >> It might possibly prevent a recurrence. >> >> regards, tom lane >> >> -- >> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-admin > > -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
