| From: | George Essig <george_essig(at)yahoo(dot)com> |
|---|---|
| To: | Ron Snyder <snyder(at)roguewave(dot)com> |
| Cc: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: putting binary data in a char field? |
| Date: | 2004-06-18 21:07:12 |
| Message-ID: | 20040618210712.91471.qmail@web53710.mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ron Snyder <snyder(at)roguewave(dot)com> wrote:
> When I changed the field to a bytea, processing time was
> significantly reduced
You should also experiment with using a TEXT field and base64 encoding to insert data and base64
decoding to select data. In my experience, this is faster than using a bytea field. Certain
characters in binary data have to be escaped properly before you can insert data. The size and
time this takes can vary. Base64 encoding is fast and will increase the binary string by 1/3.
George Essig
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2004-06-18 21:29:25 | Re: INSERT ON DUPLICATE KEY UPDATE |
| Previous Message | Eduardo Pérez Ureta | 2004-06-18 20:46:30 | Re: INSERT ON DUPLICATE KEY UPDATE |