Re: Posgresql Log: lots of parse statements - Mailing list pgsql-general

From Vikas Sharma
Subject Re: Posgresql Log: lots of parse statements
Date
Msg-id CAN6gwKxgCOmM+7iJRQWh42GbC8e4jbjHQSGV2n6f9Zc+BJ6jMA@mail.gmail.com
Whole thread Raw
In response to Re: Posgresql Log: lots of parse statements  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Posgresql Log: lots of parse statements  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Posgresql Log: lots of parse statements  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
Thanks David,

But why are there so many parse statement occurances for one query? Does postgres parse the statement everytime before  execution or parse the query only first time it is loaded in memory and reuse the same parsed plan until it ages out of memory?.

In the log I can see these parse statement occurances about 400 times in a day and everytime taking longer than 15 secs.

Regards
Vikas

On Mar 1, 2018 15:30, "David G. Johnston" <david.g.johnston@gmail.com> wrote:
On Thu, Mar 1, 2018 at 8:23 AM, Vikas Sharma <shavikas@gmail.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.
 

pgsql-general by date:

Previous
From: Steve Atkins
Date:
Subject: Re: Enforce primary key on every table during dev?
Next
From: Ron Johnson
Date:
Subject: Re: Version upgrade: is restoring the postgres database needed?