Re: One source of constant annoyance identified - Mailing list pgsql-general

From Markus Wollny
Subject Re: One source of constant annoyance identified
Date
Msg-id 2266D0630E43BB4290742247C8910575014CE2CA@dozer.computec.de
Whole thread Raw
In response to One source of constant annoyance identified  ("Markus Wollny" <Markus.Wollny@computec.de>)
Responses Re: One source of constant annoyance identified  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hello!

Scanning google for strange backend behaviour of PostgreSQL I stumbled
over the following bug-report:

http://postgresql.linux.cz/mhonarc/pgsql-ports/1999-01/msg00001.html

It's referring to a very old version of PostgreSQL (6.0), but could it
be that we suffer from the very same phenomenon? I do notice "connection
reset by peer" messages in the logfile - I always thought that this
happened when a user terminated his request or a connection broke
because of other (mostly harmless) reasons.

Now to me it seems quite likely that our backends sort of "go to sleep",
too, hogging memory and (for some reason) processing time as well.

Has the mentioned bug report been adressed since then?

Regards,

Markus



pgsql-general by date:

Previous
From: "Markus Wollny"
Date:
Subject: Why is index disregarded when querying a timestamp?
Next
From: terry@greatgulfhomes.com
Date:
Subject: Truncation error