| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
| Cc: | Radosław Smogura <rsmogura(at)softperience(dot)eu>, David North <dtn(at)corefiling(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: bytea columns and large values |
| Date: | 2011-10-01 20:05:41 |
| Message-ID: | CAHyXU0wCp0mwN5bWTh3F8072rMqXsJHRKiHctVXjtkt3CWXS-g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Oct 1, 2011 at 4:27 AM, Dmitriy Igrishin <dmitigr(at)gmail(dot)com> wrote:
> Hey Merlin,
>
>> The lo interface sucks but it's slightly better on resources for
>> really huge bytea and tends to be more consistently implemented in
>> database drivers. If I was doing this, I would of course be crafting
>> a carefully generated client in C, using libpqtypes, which is the gold
>> standard for sending bytea against which all others should be judged.
>
> I am sorry, but why the Large Objects interface sucks?
hm, good question. well, it's not sql and is outside the type system.
imo, bytea is really the way to go for sending binary. also, if it
turns out that we need to add features to send large pieces of data,
it should not be specific to bytea.
merlin
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitriy Igrishin | 2011-10-01 20:15:16 | Re: bytea columns and large values |
| Previous Message | Andrew Sullivan | 2011-10-01 19:29:45 | Re: How to find freak UTF-8 character? |