| From: | Siraj G <tosiraj(dot)g(at)gmail(dot)com> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Performance issue - Seq Scan |
| Date: | 2025-01-20 08:40:54 |
| Message-ID: | CAC5iy63JA0nMnJeCUTDBGNZkZomQ7hTp1eHCsWd3bJY2CGpAkQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hello Experts!
We had a performance issue with a SQL that used to complete in a few
milliseconds, was taking over 14seconds. We had to run *analyze *on 3
tables to get the idle performance back.
When the performance was not optimal, we noticed sequential scans even with
indexes created.
The tables and their count:
coverage_details = 529628595
customer_details = 81721669
policy_details = 116909729
PgSQL version is:
PostgreSQL 15.7 on x86_64-pc-linux-gnu, compiled by Debian clang version
12.0.1, 64-bit
One more information is that we noticed this started happening (in the
destination) after an ETL job completed the load (regular load). *Just
wanted to know if any follow up actions we should do after such data loads,
eg., analyze or vacuum. *We do have autovacuum on, with default values.
Regards
Siraj
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2025-01-20 09:34:31 | Re: Performance issue - Seq Scan |
| Previous Message | Tim Gerber | 2025-01-20 06:08:09 | Re: pg_basebackup failing |