MIME-Version: 1.0
References: <CAD=mzVUo9UpTw7F_8HKDK19ZmO6tE6Cfa4T-7i1J_QGfi6NpOw@mail.gmail.com>
 <CAAPsdhd=JfvVaNMnJ1eUAuBts3664Q0r8JE-OBijvEuTQO4P3w@mail.gmail.com>
In-Reply-To: <CAAPsdhd=JfvVaNMnJ1eUAuBts3664Q0r8JE-OBijvEuTQO4P3w@mail.gmail.com>
From: sud <suds1434@gmail.com>
Date: Sun, 7 Jul 2024 01:32:33 +0530
Message-ID: <CAD=mzVUiYcg06iTaPaBEFa0utyu8vFCK5nEH0=fhM3eBjTZ9mQ@mail.gmail.com>
Subject: Re: Load a csv or a avro?
To: Kashif Zeeshan <kashi.zeeshan@gmail.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000d1fea5061c99a982"
Archived-At: <https://www.postgresql.org/message-id/CAD%3DmzVUiYcg06iTaPaBEFa0utyu8vFCK5nEH0%3DfhM3eBjTZ9mQ%40mail.gmail.com>
Precedence: bulk

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

On Fri, Jul 5, 2024 at 3:27=E2=80=AFPM Kashif Zeeshan <kashi.zeeshan@gmail.=
com>
wrote:

> Hi
>
> There are different data formats available, following are few points for
> there performance implications
>
> 1. CSV : It's easy to use and widely supported but it can be slower due t=
o
> parsing overload.
> 2. Binary : Its faster to load but not human understandable.
>
> Hope this helps.
>
> Regards
> Kashif Zeeshan
>
>>
>>
 My understanding was that it will be faster to load .csv as it is
already being mapped to table rows and columns whereas in case of .avro the
mapping has to be done so that the fields in the avro can be mapped to the
columns in the table appropriately and that will be having additional
overhead. Is my understanding correct?

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Fri, Jul 5, 2024 at 3:27=E2=80=AFPM Ka=
shif Zeeshan &lt;<a href=3D"mailto:kashi.zeeshan@gmail.com">kashi.zeeshan@g=
mail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div dir=3D"ltr">Hi<div><br></div><div>There are different data for=
mats available, following are few points for there performance implications=
</div><div><br></div><div>1. CSV : It&#39;s easy to use and widely=C2=A0sup=
ported but it can be slower due to parsing overload.</div><div>2. Binary : =
Its faster=C2=A0to load but not human understandable.</div><div><br></div><=
div>Hope this=C2=A0helps.</div><div><br></div><div>Regards</div><div>Kashif=
 Zeeshan</div></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><br></blockquote></div></blockquote><div><br></div><d=
iv>=C2=A0My understanding was that it will be faster to load .csv as it is =
already=C2=A0being mapped to table rows and columns whereas=C2=A0in case of=
=C2=A0.avro the mapping has to be done so that the fields in the avro can b=
e mapped to the columns in the table appropriately and that will be having =
additional overhead. Is my understanding correct?</div></div></div>

--000000000000d1fea5061c99a982--