From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Question regarding DEALLOCATE pdo_stmt_00000001 |
Date: | 2014-05-21 23:50:05 |
Message-ID: | 1400716205296-5804672.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Laurentius Purba wrote
> Hello all,
>
> I've been seeing lots of this processes in my database DEALLOCATE
> pdo_stmt_00000001 with idle state.
>
> Executing *select * from pg_stat_activity where query like
> 'DEALLOCATE%';*I can see some of them are idle for +/- 30 minutes, and
> there is one idle
> for 4 days.
>
> When I checked one of the pid by executing *select * from pg_stat_activity
> where pid = 63882;* (for example), after few minutes (can be longer), it
> became *DISCARD ALL* and after that it was removed from pg_stat_activity.
>
> I was wondering if this is the normal behavior, since some of them are
> idle
> for +/- 30 minutes.
>
> I am using PostgreSQL 9.3.2 and PgBouncer.
>
> Any help is appreciated.
>
> Regards,
>
> -Laurentius
Yes.
9.3 - On an idle connection the value of query is the last executed query -
which in this case is some form session cleanup command before returning the
connection to the pool.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Question-regarding-DEALLOCATE-pdo-stmt-00000001-tp5804667p5804672.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2014-05-22 02:35:54 | Re: Lock during insert statement |
Previous Message | AI Rumman | 2014-05-21 23:42:15 | Re: Lock during insert statement |