Re: Change in Log Format and Prepared Statements

From: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: Alexander Stanier <alexander(dot)stanier(at)egsgroup(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Change in Log Format and Prepared Statements
Date: 2012-09-17 05:15:45
Message-ID: 5056B201.5020809@ringerc.id.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On 09/14/2012 03:24 AM, Dave Cramer wrote:
> Yes, the new driver uses V3 protocol which uses prepared statements,
> named and un-named. I think the 3 durations may be due to the prepare
> and execute.

I noticed this as well, and wasn't entirely thrilled with the effects on
logging.

I wonder if Pg can be convinced to suppress the non-execution times, or
merge them to report a single statement execution time. I'll poke -hackers.

--
Craig Ringer

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Alexander Stanier 2012-09-17 06:45:14 Re: Change in Log Format and Prepared Statements
Previous Message Craig Ringer 2012-09-17 05:06:39 Re: Bug : FAST_NUMBER_FAILED when getting NaN on BigDecimal