| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Vikas Sharma <shavikas(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Posgresql Log: lots of parse statements |
| Date: | 2018-03-01 15:30:36 |
| Message-ID: | CAKFQuwY_LD2ZX1eRXKU5ckCK7CtnDD+JC4v746arMWstpQcLAg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Mar 1, 2018 at 8:23 AM, Vikas Sharma <shavikas(at)gmail(dot)com> wrote:
> Hi All,
>
> I need help to understand this please. I was looking to do performance
> tuning on slow queries so have stated logging queries taking more than 15
> secs. In the postgresql log I can see a query which appears only as
> "parse" while others appear as execute.
> [...]
> I don't see this query to appear as execute, so how can find out how much
> time it's taking to execute? does this parse timing includes execute also?
>
The most likely explanation is that executing the already parsed query
takes less than 15 seconds and so doesn't appear due to your filter.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2018-03-01 16:15:42 | Re: Version upgrade: is restoring the postgres database needed? |
| Previous Message | Vikas Sharma | 2018-03-01 15:23:53 | Posgresql Log: lots of parse statements |