MIME-Version: 1.0
References: <937562047.1752859.1721295502145.ref@mail.yahoo.com> <937562047.1752859.1721295502145@mail.yahoo.com>
In-Reply-To: <937562047.1752859.1721295502145@mail.yahoo.com>
From: Kashif Zeeshan <kashi.zeeshan@gmail.com>
Date: Thu, 18 Jul 2024 14:42:41 +0500
Message-ID: <CAAPsdhd0Ln==fwX04d+ePoxLheA2LBz7GXgAjcycZQKBPOD6rg@mail.gmail.com>
Subject: Re: Re. Select with where condition times out
To: "sivapostgres@yahoo.com" <sivapostgres@yahoo.com>
Cc: Postgresql General Group <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000fd19b8061d8266d1"
Archived-At: <https://www.postgresql.org/message-id/CAAPsdhd0Ln%3D%3DfwX04d%2BePoxLheA2LBz7GXgAjcycZQKBPOD6rg%40mail.gmail.com>
Precedence: bulk

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

Hi

It can be caused due to Table Bloat, table bloat can slow down queries. Use
the pg_repack extension or VACUUM FULL to try ti fix this table bloat issue=
.
You can refer to following link
https://supabase.com/blog/postgres-bloat

Regards
Kashif Zeeshan

On Thu, Jul 18, 2024 at 2:38=E2=80=AFPM sivapostgres@yahoo.com <
sivapostgres@yahoo.com> wrote:

> Hello,
> PG V11
>
> Select count(*) from table1
> Returns 10456432
>
> Select field1, field2 from table1 where field3> '2024-07-18 12:00:00'
> Times out
>
> The above query was working fine for the past 2 years.
>
> Backup was taken a day back.  Need to recover complete data as far as
> possible.
>
> Any possible way(s) to do this?
>
> BKR Sivaprakash
>
>
> Yahoo Mail: Search, organise, conquer
> <https://mail.onelink.me/107872968?pid=3DNativePlacement&c=3DGlobal_Acqui=
sition_YMktg_315_EmailSignatureGrowth_YahooMail:Search,Organize,Conquer&af_=
sub1=3DAcquisition&af_sub2=3DGlobal_YMktg&af_sub3=3D&af_sub4=3D100000945&af=
_sub5=3DOrganizeConquer__Static_>
>

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

<div dir=3D"ltr">Hi<div><br></div><div>It can be caused due to Table Bloat,=
 table bloat can slow down queries. Use the pg_repack extension or VACUUM F=
ULL to try ti fix this table bloat issue.</div><div>You can refer to follow=
ing link</div><div><a href=3D"https://supabase.com/blog/postgres-bloat">htt=
ps://supabase.com/blog/postgres-bloat</a><br></div><div><br></div><div>Rega=
rds</div><div>Kashif Zeeshan</div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 18, 2024 at 2:38=E2=80=AFPM <=
a href=3D"mailto:sivapostgres@yahoo.com">sivapostgres@yahoo.com</a> &lt;<a =
href=3D"mailto:sivapostgres@yahoo.com">sivapostgres@yahoo.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-left:1ex">Hello,<div>PG =
V11</div><div><br></div><div>Select count(*) from table1</div><div>Returns =
10456432</div><div><br></div><div>Select field1, field2 from table1 where f=
ield3&gt; &#39;2024-07-18 12:00:00&#39;=C2=A0</div><div>Times out</div><div=
><br></div><div>The above query was working fine for the past 2 years.=C2=
=A0=C2=A0</div><div><br></div><div>Backup was taken a day back.=C2=A0 Need =
to recover complete data as far as possible.</div><div><br></div><div>Any p=
ossible way(s) to do this?</div><div><br></div><div>BKR Sivaprakash=C2=A0</=
div><div><br><br><div id=3D"m_2602144116742344041ymail_android_signature"><=
a id=3D"m_2602144116742344041ymail_android_signature_link" href=3D"https://=
mail.onelink.me/107872968?pid=3DNativePlacement&amp;c=3DGlobal_Acquisition_=
YMktg_315_EmailSignatureGrowth_YahooMail:Search,Organize,Conquer&amp;af_sub=
1=3DAcquisition&amp;af_sub2=3DGlobal_YMktg&amp;af_sub3=3D&amp;af_sub4=3D100=
000945&amp;af_sub5=3DOrganizeConquer__Static_" target=3D"_blank">Yahoo Mail=
: Search, organise, conquer</a></div></div></blockquote></div>

--000000000000fd19b8061d8266d1--