Re: Perfomance issue. statement in the log file..

From: Bala Venkat <akpgeek(at)gmail(dot)com>
To: Roxanne Reid-Bennett <rox(at)tara-lu(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Perfomance issue. statement in the log file..
Date: 2016-02-24 15:41:24
Message-ID: CACnhOf+yQ7n0E6xe_YWLbM80uq8TDbHVHy3QVz1YgynSsDapiw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thank you. That will help us. We are changing the settings. We are running
9.0.4. Appreciate your time and help

On Tue, Feb 23, 2016 at 3:20 PM, Roxanne Reid-Bennett <rox(at)tara-lu(dot)com>
wrote:

> On 2/23/2016 11:57 AM, Bala Venkat wrote:
>
>> Dear All -
>>
>> We are seeing lot of these statements in the log file. We have 2
>> functions . Submit and update . Between submit and update which will int
>> the process, the messages are appearning. The process is very slow. We
>> don't know if this the main reason for the performance issue
>>
>> Can you please help ? if any one has come across this issue and
>> resolved. Appreciate your time.
>>
>> 2016-02-23 18:11:24 GMT IpAddress(33946) user=UserName , db=testLOG:
>> execute <unnamed>: SELECT 1 FROM pg_catalog.pg_attrdef WHERE adrelid = $1
>> AND adn
>> um = $2 AND pg_catalog.pg_get_expr(adbin, adrelid) LIKE
>> '%nextval(%'
>> 2016-02-23 18:11:24 GMT IpAddress(33946) user=UserName , db=testDETAIL:
>> parameters: $1 = '3003958', $2 = '1'
>> 2016-02-23 18:11:24 GMT IpAddress(33946) user=UserName , db=testLOG:
>> duration: 0.059 ms
>> 2016-02-23 18:11:24 GMT IpAddress(33946) user=UserName , db=testLOG:
>> duration: 0.117 ms
>> 2016-02-23 18:11:24 GMT IpAddress(33946) user=UserName , db=testLOG:
>> duration: 1.087 ms
>> 2016-02-23 18:11:24 GMT IpAddress(33946) user=UserName , db=testLOG:
>> execute <unnamed>: SELECT attnotnull FROM pg_catalog.pg_attribute WHERE
>> attrelid =
>> $1 AND attnum = $2
>> 2016-02-23 18:11:24 GMT IpAddress(33946) user=UserName , db=testDETAIL:
>> parameters: $1 = '3003958', $2 = '1'
>>
>
> ...
> Having done a cursory search for "SELECT attnotnull FROM
> pg_catalog.pg_attribute WHERE attrelid ="
> It appears your potential culprit is a JDBC or ODBC (or ORM managed)
> connection querying meta-data over and over.
> To identify connection information, back in 2010 [so... your mileage may
> vary] Tom suggested the use of:
>
> See log_connections and log_disconnections. You probably want to
> add PID to log_line_prefix, too, so that you can associate different
> log entries for the same session.
>
>
> Version of Postgres and the execution environment of the 2 functions.
> [e.g. pgsql, PL/?, code etc] might provide more input to help identify a
> more specific answer.
>
> Roxanne
>
> --
> [At other schools] I think the most common fault in general is to teach
> students how to pass exams instead of teaching them the science.
> Donald Knuth
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Paul Jungwirth 2016-02-24 17:44:37 Re: Ubuntu and Rails postgresql setup
Previous Message Seamus Abshere 2016-02-24 15:23:38 uuid gin operator class - why not include for everybody?