On Fri, 2024-02-02 at 10:14 +0530, veem v wrote:
> On Fri, 2 Feb 2024 at 02:43, Laurenz Albe 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 analy
On Fri, 2 Feb 2024 at 02:43, Laurenz Albe 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
> >
On Thu, Feb 1, 2024 at 4:13 PM Laurenz Albe
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
>
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 furth
Hello All,
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. It's a UI query showing top 50 rows and is sup
