From: scott.marlowe <scott.marlowe@ihs.com>
To: Medi Montaseri <medi.montaseri@intransa.com>
Cc: pgsql General List <pgsql-general@postgresql.org>
Subject: Re: Closing inactive connections OR user connections limits
Date: Wed, 20 Nov 2002 17:09:34 -0700 (MST)
Message-ID: <Pine.LNX.4.33.0211201703060.21721-100000@css120.ihs.com> (raw)
In-Reply-To: <3DDC2062.7000109@intransa.com>
On Wed, 20 Nov 2002, Medi Montaseri wrote:
> So I think you have shown that 7.2 achieves this by skiping current
> transactions....
> Thank you
You're welcome. Having re-read my response, I realize now it sounded
harsh, and I certainly didn't mean it that way.
Usually, when a bug shows up here involving race conditions they're so
rare that I've never run into them. And usually when Postgresql DOES make
a mistake, it's something like permanently making a tuple undeleteable or
non-vacuumable, i.e. it tends to err on the side of caution.
7.2 rocks by the way. It's rock solid for us, and we use it for dozens
and dozens of projects where I work. The Postgresql hackers have what I
call a "NASA space shot" mentality. Quite refreshing in a world of
"weekend drag racer" developers.
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-sql@postgresql.org
Cc: scott.marlowe@ihs.com, medi.montaseri@intransa.com, pgsql-general@postgresql.org
Subject: Re: Closing inactive connections OR user connections limits
In-Reply-To: <Pine.LNX.4.33.0211201703060.21721-100000@css120.ihs.com>
* 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