From: Dean Gibson (DB Administrator) <postgresql@mailpen.com>
To: pgsql-performance@lists.postgresql.org
Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
Date: Sat, 29 May 2021 13:17:40 -0700
Message-ID: <82627a7c-98ca-b60c-c49a-0f1ca132a639@mailpen.com> (raw)
In-Reply-To: <40d30a5c-ae45-3caf-f74a-f091e8ad0a2c@yandex.ru>
References: <88dec70b-eb63-0b72-0b5d-253851ef127b@mailpen.com>
<163214e4-0588-230b-9ed5-f682087e0e18@wi3ck.info>
<4e238cc5-f63e-0435-63bf-2515500d5424@dunslane.net>
<20210528213052.GC5649@momjian.us>
<E007EEB7-097D-4D0E-9C4D-C8BB28810E7F@thebuild.com>
<cf15c19d-43d8-95ff-17a0-ded099f70861@mailpen.com>
<40d30a5c-ae45-3caf-f74a-f091e8ad0a2c@yandex.ru>
On 2021-05-28 22:24, Alexey M Boltenkov wrote:
> On 05/29/21 07:08, Dean Gibson (DB Administrator) wrote: [deleted]
>
> BTW what is the planner reason to not use index in v13.2? Is index in
> corrupted state? Have you try to reindex index
> "FccLookup"."_LicStatus_pkey" ?
>
> 1.5M of seqscan's are looking really bad.
>
> SubPlan 2
> -> Limit (cost=0.15..8.17 rows=1 width=32)
> (actual time=0.006..0.007 rows=1 loops=55)
> -> *Index Scan using "_LicStatus_pkey" on
> "_LicStatus"* (cost=0.15..8.17 rows=1 width=32) (actual
> time=0.005..0.005 rows=1 loops=55)
> Index Cond: ("_HD".license_status =
> status_id)
>
>
> SubPlan 2
> -> Limit (cost=0.00..1.07 rows=1 width=13)
> (actual time=0.001..0.001 rows=1 loops=1487153)
> -> *Seq Scan on "_LicStatus"*
> (cost=0.00..1.07 rows=1 width=13) (actual time=0.000..0.000 rows=1
> loops=1487153)
> Filter: ("_HD".license_status =
> status_id)
> Rows Removed by Filter: 1
>
Doing your REINDEX didn't help. Now in the process of reindexing the
entire database. When that's done, I'll let you know if there is any
improvement.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: postgresql@mailpen.com, pgsql-performance@lists.postgresql.org
Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
In-Reply-To: <82627a7c-98ca-b60c-c49a-0f1ca132a639@mailpen.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox