| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | veem v <veema0000(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Query running longer |
| Date: | 2024-02-01 21:13:39 |
| Message-ID: | 64de715ce18ab55159468cfdd8b8958f55eb8808.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2024-02-02 at 02:27 +0530, veem v wrote:
> We have the below query which is running for ~45 seconds on postgres aurora reader instance.
> I have captured the explain analyze. Want to understand, where exactly the resources are
> getting spent and if we can be able to optimize it further.
Aurora <> PostgreSQL, but here is what I can see:
- The index scan on SCHEMA1."TAB2" has to check 2 million extra
rows because "work_mem" is too small. Almost the complete time
is spent there.
- You may be getting a bad plan, because the statistics on
SCHEMA1.TAB4 are either out of date or not detailed enough,
which makes PostgreSQL underestimate the result size.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2024-02-01 23:22:09 | Re: Query running longer |
| Previous Message | veem v | 2024-02-01 20:57:01 | Query running longer |