From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(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:15:16 |
Message-ID: | CAAfz9KOUKjVKZbUm1=8081FGCSMij74=990zfgScO7_n62=5ZQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2011/10/2 Merlin Moncure <mmoncure(at)gmail(dot)com>
> 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.
>
But at the moment, the only way to put/get the data piecewise
is to use LOBs.
>
> merlin
>
> merlin
>
--
// Dmitriy.
From | Date | Subject | |
---|---|---|---|
Next Message | Leif Biberg Kristensen | 2011-10-01 21:16:06 | Re: How to find freak UTF-8 character? |
Previous Message | Merlin Moncure | 2011-10-01 20:05:41 | Re: bytea columns and large values |