[pgpool-general: 3190] connection with DISCARD ALL

Yaron Naveh yaronn01 at gmail.com
Thu Sep 25 07:20:14 JST 2014


Hi

What does it mean when a connection in Postgres has last query DISCARD ALL
for several days? All timeouts settings are for max 300 seconds.
I am planning to migrate 3.3.3-->3.3.4 but it takes time on production so I
am trying to understand if this issue is known. Note that pgpool does not
know anything about this connection anymore so it is different than defect
#107 which 3.3.4 fix.


SELECT * FROM pg_stat_activity LIMIT 1


  datid  |  datname   | pid  | usesysid |     usename     |
application_name |  client_addr   | client_hostname | client_port |
backend_start         | xact_start |          query_start          |
  state_change         | waiting | state |    query
---------+------------+------+----------+-----------------+------------------+----------------+-----------------+-------------+-------------------------------+------------+-------------------------------+------------------------------+---------+-------+--------------
 2124078 | db_name | 8508 |    16395 | user_name |                  |
11.134.32.116 |                 |       49032 | 2014-09-22
01:23:18.694586-07 |            | 2014-09-22 01:28:20.474515-07 |
2014-09-22 01:28:20.47483-07 | f       | idle  |  DISCARD ALL

Thanks,
Yaron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20140925/67842148/attachment.html>


More information about the pgpool-general mailing list