MIME-Version: 1.0
From: Wasim Devale <wasimd60@gmail.com>
Date: Thu, 7 Nov 2024 14:46:26 +0530
Message-ID: 
 <CAB5fag5qfKqQLh52NbvRT1TmALC6dSx1wfLfrLSmHueYAYQx-Q@mail.gmail.com>
Subject: ON CONFLICT Clause used on partition tables
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>,
	pgsql-admin <pgsql-admin@postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000069779006264f176c"
Archived-At: 
 <https://www.postgresql.org/message-id/CAB5fag5qfKqQLh52NbvRT1TmALC6dSx1wfLfrLSmHueYAYQx-Q%40mail.gmail.com>
Precedence: bulk

--00000000000069779006264f176c
Content-Type: text/plain; charset="UTF-8"

Hi All

I encountered the insert clause "ON CONFLICT DO update" slowing down the
insertion in the partition tables what might be the reason. I used
timestamp partion key.

I understand the uniqueness can not be maintained across all partions but
the partion key must take care of it globally for inserting bulk data from
CSV files.

Please help on this.

Thanks,
Wasim

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

<div dir=3D"auto">Hi All<div dir=3D"auto"><br></div><div dir=3D"auto">I enc=
ountered the insert clause &quot;ON CONFLICT DO update&quot; slowing down t=
he insertion in the partition tables what might be the reason. I used times=
tamp partion key.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">=
I understand the uniqueness can not be maintained across all partions but t=
he partion key must take care of it globally for inserting bulk data from C=
SV files.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Please help on=
 this.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks,</div><div=
 dir=3D"auto">Wasim</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br>=
</div></div>

--00000000000069779006264f176c--