> -----Original Message----- > From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general- > ow...@postgresql.org] On Behalf Of Victor Sterpu > Sent: Wednesday, April 02, 2014 2:25 PM > To: Victor Sterpu; Merlin Moncure > Cc: PostgreSQL General > Subject: Re: [GENERAL] Lock problem > > I'm sure is not right, but is a there a server side solution for such > sitations? > A configuration - timeout for idle transactions. >
I don't think PG has such configuration parameter. But, you could easily write a function (say in PgPlSQL) and run it on schedule, where you could check "IDLE IN TRANSACTION" session and compare their start_time to system time, and then based on your criteria you could kill suspect session/transaction. But this could be dangerous; some long-running transactions could be perfectly valid. Regards, Igor Neyman -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
