| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | 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 23:22:09 |
| Message-ID: | CANzqJaC9e+08ndpLeBKJ9eQ4oEVSKdOEoQfdn0FR+G5aHpHrLg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 1, 2024 at 4:13 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> 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.
>
Is that these numbers?
Buffers: shared hit=xxxxxx read=22xxxxx
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Angelico | 2024-02-02 02:20:40 | Logical replication and AFTER UPDATE triggers [PG 16] |
| Previous Message | Laurenz Albe | 2024-02-01 21:13:39 | Re: Query running longer |