0005731: exchange potentially leaks DB handles

ID	Project	Category	View Status	Date Submitted	Last Update
0005731	Taler	exchange	public	2019-05-24 17:09	2019-12-20 18:12

Reporter	Florian Dold	Assigned To	Christian Grothoff	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	fixed
Product Version	0.5
Target Version	0.6	Fixed in Version	0.6

Summary	0005731: exchange potentially leaks DB handles
Description	We get the following in the PostgreSQL log: 2019-05-23 18:04:05.185 CEST [12458] demo-blue@talerdemo FATAL: remaining connection slots are reserved for non-replication superuser connections This indicates that the exchange might leak DB handles ... Can we add some tracking/logging for this?
Tags	No tags attached.

Date Modified	Username	Field	Change
2019-05-24 17:09	Florian Dold	New Issue
2019-05-24 17:09	Florian Dold	Status	new => assigned
2019-05-24 17:09	Florian Dold	Assigned To	=> Christian Grothoff
2019-05-25 10:43	Christian Grothoff	Status	assigned => informing
2019-05-25 10:43	Christian Grothoff	Resolution	open => fixed
2019-05-25 10:43	Christian Grothoff	Fixed in Version	=> 0.6
2019-05-25 10:43	Christian Grothoff	Note Added: 0014442
2019-05-25 10:43	Christian Grothoff	Product Version	=> 0.5
2019-05-25 10:43	Christian Grothoff	Target Version	=> 0.6
2019-12-20 18:12	Christian Grothoff	Status	informing => closed

Christian Grothoff 2019-05-25 10:43 manager ~0014442	I believed we established in private messages that our setup would have legitimately used >= 128 connections and the server was ill-configured to only accept 100. As per Florian's PM, the Postgres configuration was fixed to address this. Hence calling this one resolved.