Re: BUG #13979: Strange pg_stat_statements results with PREPARE/EXECUTE

From: Kasahara Tatsuhito <kasahara(dot)tatsuhito(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13979: Strange pg_stat_statements results with PREPARE/EXECUTE
Date: 2016-02-24 17:53:05
Message-ID: CAP0=ZVKF-iKUw_2KhXegc3akVZFc6OKhOobnhZN-ohg8suvJeA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

2016-02-24 0:32 GMT+09:00 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>:
> What do you think the following statement does?
>
> PreparedStatement ps1 = con.prepareStatement(sql1);
I think above statement would performed "PREAPRE".
But sometimes those were counted as PREPARE, or sometimes were
counted as normal SELECT.
So, I was little confused...

But I see it's a restrictions of current postgres's design.

Best regards,
--
Tatsuhito Kasahara
kasahara.tatsuhito _at_ gmail.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kasahara Tatsuhito 2016-02-24 18:05:12 Re: BUG #13979: Strange pg_stat_statements results with PREPARE/EXECUTE
Previous Message martin.klima 2016-02-24 16:36:56 BUG #13987: Refreshing materialized view prevents changing rights during restore