| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | Arthur Ramsey <arthur(dot)ramsey(at)code42(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Sequential scan faster than index |
| Date: | 2023-02-21 10:41:19 |
| Message-ID: | CAKoxK+5E_vtSi06yWDaFiH8w3HgQFU2YnAMBJq3cNO2j=RuqkA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 21, 2023 at 10:30 AM Arthur Ramsey <arthur(dot)ramsey(at)code42(dot)com> wrote:
>
> I'm trying to figure out why a sequential scan is out performing. I've tried psql 13.7, psql14.6 and REINDEX. The REINDEX didn't help. This is on an RDS instance that's a db.m5.large (2 * vCPU, 8 GB memory) with 200 storage on io1 with 10000 provisioned IOPS. I restarted the RDS instance in between each test.
>
At glance, it seems there are very few rows to operate on:
-> Seq Scan on t_status_175000000_176000000 t_status_39
(cost=0.00..13.80 rows=380 width=14) (actual time=0.009..0.010 rows=0
loops=1)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2023-02-21 11:06:25 | Re: Sequential scan faster than index |
| Previous Message | Peter Geoghegan | 2023-02-21 05:50:56 | Re: Automatic aggressive vacuum on almost frozen table takes too long |