Обсуждение: Strange activity of prepared queries

Hi!
I have pgBadger report with strange data about prepared queries I cannot
interpret by myself. If anybody could help me with interpretation, would be
greatly appreciated.
In first half of the day pgBadger shows there is no prepare statements and
all queries are binded - how is that possible if average duration of session
is only 4m16s, not 15 hours?

Hour    Prepare    Bind    Bind/Prepare    Percentage of prepare
0    0    4,059    4,059.00    0.00%
1    0    341    341.00    0.00%
2    0    8    8.00    0.00%
3    0    16    16.00    0.00%
4    0    28    28.00    0.00%
5    0    6    6.00    0.00%
6    0    350    350.00    0.00%
7    0    2,35    2,350.00    0.00%
8    0    1,999    1,999.00    0.00%
9    0    2,383    2,383.00    0.00%
10    3    870    290.00    0.34%
11    0    1,941    1,941.00    0.00%
12    2    1,397    698.50    0.14%
13    0    798    798.00    0.00%
14    0    1,445    1,445.00    0.00%
15    1,707,090    1,707,503    1.00    99.93%
16    2,133,960    2,134,001    1.00    99.94%
17    1,793,804    1,793,851    1.00    99.93%
18    1,745,064    1,745,095    1.00    99.94%
19    1,067,248    1,067,288    1.00    99.90%
20    937,137    937,142    1.00    99.88%
21    596,606    596,603    1.00    34.43%
22    711,941    711,945    1.00    58.58%
23    816,353    816,37    1.00    99.86%




--
View this message in context: http://postgresql.nabble.com/Strange-activity-of-prepared-queries-tp5932990.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

On Fri, 2016-12-02 at 07:04 -0700, pinker wrote:
>
> Hi!
> I have pgBadger report with strange data about prepared queries I
> cannot
> interpret by myself. If anybody could help me with interpretation,
> would be
> greatly appreciated.
> In first half of the day pgBadger shows there is no prepare
> statements and
> all queries are binded - how is that possible if average duration of
> session
> is only 4m16s, not 15 hours?
You haven't told us what parameters you use, which is a crucial piece
of information. For example it's possible that most of the time the
planning is fast enough not to be logged, so it's invisible for
pgbadger.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services