From: | Steven Pousty <steve(dot)pousty(at)gmail(dot)com> |
---|---|
To: | Bzzzz <lazyvirus(at)gmx(dot)com> |
Cc: | Goke Aruna <goksie(at)gmail(dot)com>, pgsql-novice(at)lists(dot)postgresql(dot)org, Babatunde Adeyemi <barbietunnie(at)gmail(dot)com> |
Subject: | Re: Slow response to my query |
Date: | 2019-11-28 16:11:43 |
Message-ID: | CAKmB1PGVTk=mEoLA2O4ZqsbmW3RDDriYXJhKsk75+BpvcLSDdw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Sounds like you should do an
EXPLAIN
in front of your query and see what the query planner is thinking. If you
can spare the 1.5 hours do an EXPLAIN ANALYZE. It should be safe as long as
you are only doing a select query.
Thanks
Steve
On Thu, Nov 28, 2019 at 7:13 AM Bzzzz <lazyvirus(at)gmx(dot)com> wrote:
> On Thu, 28 Nov 2019 10:38:22 +0100
> Goke Aruna <goksie(at)gmail(dot)com> wrote:
>
> > however, do you have ant specific test to run with the pgbench?
>
> Nope, I don't have the man in mind - read it and adapt your test to your
> problem.
>
> BTW, you did not say it, but I suppose you're using rust not SSDz?
>
> > I have about 6 of my columns indexed.
>
> Are they involved in your query?
>
> > I will share the test query once i got the queries from the UI man.
>
> ? Without the table and it's indexes structures plus the query, it's like
> a car without an engine (or a chauffeur)…
>
> Also, read this:
> https://hakibenita.com/be-careful-with-cte-in-postgre-sql
> and that:
> https://www.2ndquadrant.com/en/blog/on-rocks-and-sand/
>
> Jean-Yves
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Goke Aruna | 2019-11-29 11:09:04 | Re: Slow response to my query |
Previous Message | Bzzzz | 2019-11-28 15:13:19 | Re: Slow response to my query |