From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mike Bridge <mike@bridgecanada.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: High CPU with 7.4.1 after running for about 2 weeks
Date: Mon, 15 Mar 2004 16:46:54 -0500
Message-ID: <7887.1079387214@sss.pgh.pa.us> (raw)
In-Reply-To: <ahi7509sakjto0b0nncmrl486ulot26vfh@4ax.com>
References: <l63t40lg2jr37uqgevign3fq4stukpihi0@4ax.com>
<7304.1079219828@sss.pgh.pa.us>
<ahi7509sakjto0b0nncmrl486ulot26vfh@4ax.com>
Mike Bridge <mike@bridgecanada.com> writes:
> But if the client dies, doesn't postgresql normally terminate the
> query that that client initiated? Or do I need to set
> statement_timeout?
The backend generally won't notice that the connection is dead until
it next tries to fetch a command from the client. So if the client
launches a long-running query and then goes away, the query will
normally complete.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, mike@bridgecanada.com
Subject: Re: High CPU with 7.4.1 after running for about 2 weeks
In-Reply-To: <7887.1079387214@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox