MIME-Version: 1.0
References: <CAEZv3cqct1WFb9KYmYa5kjdxfVK8JEFdzbJ5bRL6b4r+XR2dug@mail.gmail.com>
 <CANzqJaBfaOvbjJYYCPPC-JKFEw=pZTGkfwL3+-t2fjP7B_9U+g@mail.gmail.com>
 <f1a0c76b-c645-4530-b768-fea480eab56e@cloud.gatewaynet.com>
 <CANzqJaCtWGeLNoVVmzJ6=S6XzptR_K6VByCtwCLRVXAHUk0fUw@mail.gmail.com> <20241016214847.yzfvfkvfnnlm2ba3@hjp.at>
In-Reply-To: <20241016214847.yzfvfkvfnnlm2ba3@hjp.at>
From: Andy Hartman <hartman60home@gmail.com>
Date: Wed, 16 Oct 2024 18:59:32 -0400
Message-ID: <CAEZv3cr3bgvmCWD_JEctbSDBHdBe6f-XmECSrEaC=n5zVLjv7Q@mail.gmail.com>
Subject: Re: Backup
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000087c2f50624a00610"
Archived-At: <https://www.postgresql.org/message-id/CAEZv3cr3bgvmCWD_JEctbSDBHdBe6f-XmECSrEaC%3Dn5zVLjv7Q%40mail.gmail.com>
Precedence: bulk

--00000000000087c2f50624a00610
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I'm on Ver16 and yes Our database has  image in a bytea field.

Running on Win22 box...

On Wed, Oct 16, 2024 at 5:49=E2=80=AFPM Peter J. Holzer <hjp-pgsql@hjp.at> =
wrote:

> On 2024-10-16 16:02:24 -0400, Ron Johnson wrote:
> > On Wed, Oct 16, 2024 at 4:00=E2=80=AFPM Achilleas Mantzios <
> > a.mantzios@cloud.gatewaynet.com> wrote:
> >     =CE=A3=CF=84=CE=B9=CF=82 16/10/24 22:55, =CE=BF/=CE=B7 Ron Johnson =
=CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5:
> >         On Wed, Oct 16, 2024 at 3:37=E2=80=AFPM Andy Hartman <
> hartman60home@gmail.com>
> >         wrote:
> [...]
> >
> >         Step 1: redesign your DB to NOT use large objects.  It's an old=
,
> slow
> >         and unmaintained data type.  The data type is what you should
> use.
> >
> >     You mean bytea I guess. As a side note, (not a fan of LOs), I had t=
he
> >     impression that certain drivers such as the JDBC support streaming
> for LOs
> >     but not for bytea? It's been a while I haven't hit the docs tho.
> >
> >
> > Our database is stuffed with images in bytea fields.  The Java
> application uses
> > JDBC and handles them just fine.
>
> Images are usually small enough (a few MB) that they don't need to be
> streamed.
>
> I don't think bytea can be streamed in general. It's just like text, you
> write and read the whole thing at once.
>
> If you have data which is too large for that and want to store it in
> bytea fields, you'll probably have to chunk it yourself (which you
> probably have to anyway because for me "so large it has to be streamed"
> implies "at least possibly larger than 1 GB").
>
>         hp
>
> --
>    _  | Peter J. Holzer    | Story must make more sense than reality.
> |_|_) |                    |
> | |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
> __/   | http://www.hjp.at/ |       challenge!"
>

--00000000000087c2f50624a00610
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">I&#39;m on Ver16 and yes Our database has=
=C2=A0 image in a bytea field.</div><div dir=3D"ltr"><br></div><div>Running=
 on Win22 box...</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr"=
 class=3D"gmail_attr">On Wed, Oct 16, 2024 at 5:49=E2=80=AFPM Peter J. Holz=
er &lt;<a href=3D"mailto:hjp-pgsql@hjp.at">hjp-pgsql@hjp.at</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2024-10-16 16=
:02:24 -0400, Ron Johnson wrote:<br>
&gt; On Wed, Oct 16, 2024 at 4:00=E2=80=AFPM Achilleas Mantzios &lt;<br>
&gt; <a href=3D"mailto:a.mantzios@cloud.gatewaynet.com" target=3D"_blank">a=
.mantzios@cloud.gatewaynet.com</a>&gt; wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0=CE=A3=CF=84=CE=B9=CF=82 16/10/24 22:55, =CE=BF/=CE=
=B7 Ron Johnson =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0On Wed, Oct 16, 2024 at 3:37=E2=80=AF=
PM Andy Hartman &lt;<a href=3D"mailto:hartman60home@gmail.com" target=3D"_b=
lank">hartman60home@gmail.com</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0wrote:<br>
[...]<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Step 1: redesign your DB to NOT=C2=A0=
use large objects.=C2=A0 It&#39;s an old, slow<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0and unmaintained data type.=C2=A0 The=
 data type is what you should use.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0You mean bytea I guess. As a side note, (not a fan =
of LOs), I had the<br>
&gt;=C2=A0 =C2=A0 =C2=A0impression that certain drivers such as the JDBC su=
pport streaming for LOs<br>
&gt;=C2=A0 =C2=A0 =C2=A0but not for bytea? It&#39;s been a while I haven=
9;t hit the docs tho.<br>
&gt; <br>
&gt; <br>
&gt; Our database is stuffed with images in bytea fields.=C2=A0 The Java ap=
plication uses<br>
&gt; JDBC and handles them just fine.<br>
<br>
Images are usually small enough (a few MB) that they don&#39;t need to be<b=
r>
streamed.<br>
<br>
I don&#39;t think bytea can be streamed in general. It&#39;s just like text=
, you<br>
write and read the whole thing at once.<br>
<br>
If you have data which is too large for that and want to store it in<br>
bytea fields, you&#39;ll probably have to chunk it yourself (which you<br>
probably have to anyway because for me &quot;so large it has to be streamed=
&quot;<br>
implies &quot;at least possibly larger than 1 GB&quot;).<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 hp<br>
<br>
-- <br>
=C2=A0 =C2=A0_=C2=A0 | Peter J. Holzer=C2=A0 =C2=A0 | Story must make more =
sense than reality.<br>
|_|_) |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 |<br>
| |=C2=A0 =C2=A0| <a href=3D"mailto:hjp@hjp.at" target=3D"_blank">hjp@hjp.a=
t</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 -- Charles Stross, &q=
uot;Creative writing<br>
__/=C2=A0 =C2=A0| <a href=3D"http://www.hjp.at/" rel=3D"noreferrer" target=
=3D"_blank">http://www.hjp.at/</a> |=C2=A0 =C2=A0 =C2=A0 =C2=A0challenge!&q=
uot;<br>
</blockquote></div>

--00000000000087c2f50624a00610--