Date: Thu, 6 May 2021 21:26:07 +0200 (CEST)
From: Andreas Joseph Krogh <andreas@visena.com>
To: Semen Yefimenko <semen.yefimenko@gmail.com>
Cc: Alexey M Boltenkov <padrebolt@yandex.ru>, luis.roberto@siscobra.com.br,
	pgsql-performance <pgsql-performance@lists.postgresql.org>
Message-ID: <VisenaEmail.2.8fd1850819f96dd.1794322fd82@tc7-visena>
In-Reply-To: 
 <CAKnyMoKbM+eQMEr1R4dk_5XmPttNJjD6ymxb4sbTmvWjqc8yRQ@mail.gmail.com>
References: 
 <CAKnyMoKUUSPiH=0QaM38GYm8UqVeR47HmX+MX+UpyL0mLERBrw@mail.gmail.com>
 <1368981627.1376962.1620317467043.JavaMail.zimbra@siscobra.com.br>
 <9a713ea4-f672-412c-70c3-34b82c275b7f@yandex.ru>
 <986d20ff-a662-6821-68f4-d5a8ba304eb7@yandex.ru>
 <CAKnyMoKbM+eQMEr1R4dk_5XmPttNJjD6ymxb4sbTmvWjqc8yRQ@mail.gmail.com>
Subject: Re: Very slow Query compared to Oracle / SQL - Server
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_Part_5_1452866116.1620329167328"
Archived-At: 
 <https://www.postgresql.org/message-id/VisenaEmail.2.8fd1850819f96dd.1794322fd82%40tc7-visena>
Precedence: bulk

------=_Part_5_1452866116.1620329167328
Content-Type: multipart/related;
	boundary="----=_Part_6_724878603.1620329167328"

------=_Part_6_724878603.1620329167328
Content-Type: multipart/alternative;
	boundary="----=_Part_7_877477471.1620329167413"

------=_Part_7_877477471.1620329167413
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


P=C3=A5 torsdag 06. mai 2021 kl. 20:59:34, skrev Semen Yefimenko <
semen.yefimenko@gmail.com <mailto:semen.yefimenko@gmail.com>>:=20
Yes, rewriting the query with an IN clause was also my first approach, but =
I=20
didn't help much.
 The Query plan did change a little bit but the performance was not impacte=
d.
CREATE INDEX idx_arcstatus_le1 ON schema.logtable ( archivestatus ) where=
=20
(archivestatus <=3D 1)=20
ANALYZE schema.logtable=20

 This resulted in this query plan:
 [...]=20

I assume (4000,4001,4002) are just example-values and that they might be=20
anything? Else you can just include them in your partial-index.=20


--
 Andreas Joseph Krogh=20
------=_Part_7_877477471.1620329167413
Content-Type: text/html;charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>P=C3=A5 torsdag 06. mai 2021 kl. 20:59:34, skrev Semen Yefimenko &lt;<=
a href=3D"mailto:semen.yefimenko@gmail.com">semen.yefimenko@gmail.com</a>&g=
t;:</div>

<blockquote style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt=
 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir=3D"ltr">Yes, rewriting the query with an IN clause was also my fir=
st approach, but I didn't help much.=C2=A0<br>
The Query plan did change a little bit but the performance was not impacted=
.<br>
=C2=A0
<blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><font=
 face=3D"monospace">CREATE INDEX idx_arcstatus_le1 ON schema.logtable ( arc=
hivestatus ) where=C2=A0(archivestatus &lt;=3D 1)</font>

<div><font face=3D"monospace">ANALYZE=C2=A0 schema.logtable</font></div>
</blockquote>

<div><br>
This resulted in this query plan:<br>
[...]</div>
</div>
</blockquote>

<div>=C2=A0</div>

<div>I assume=C2=A0(4000,4001,4002) are just example-values and that they m=
ight be anything? Else you can just include them in your partial-index.</di=
v>

<div class=3D"visena-email-signature" data-visena-message-id=3D"&lt;VisenaE=
mail.2.8fd1850819f96dd.1794322fd82@tc7-visena>">
<div>
<div>=C2=A0</div>

<div>--<br>
Andreas Joseph Krogh</div>
</div>
</div>
------=_Part_7_877477471.1620329167413--

------=_Part_6_724878603.1620329167328--

------=_Part_5_1452866116.1620329167328--