From: Greg Stark <gsstark@mit.edu>
To: L J Bayuk <ljb220@mindspring.com>
Cc: Nigel J. Andrews <nandrews@investsystems.co.uk>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: pgin.tcl pg_exec_prepared slow (was: Released...)
Date: 06 Jul 2004 21:44:17 -0400
Message-ID: <873c44sia6.fsf@stark.xeocode.com> (raw)
In-Reply-To: <20040706010731.GA15183@bxlbisnugqvi.mindspring.com>
References: <24110.1087945736@sss.pgh.pa.us>
<Pine.LNX.4.21.0406302310340.12226-100000@ponder.fairway2k.co.uk>
<20040706010731.GA15183@bxlbisnugqvi.mindspring.com>
L J Bayuk <ljb220@mindspring.com> writes:
> Other messages from the client are typically replied to and/or ACK'd in
> under 1 ms, according to Ethereal. I don't know why this message takes so
> much longer to ACK, nor why the client waits for the ACK. I'm sure it isn't
> the backend; I don't think it is Tcl; it could be something in the TCP
> stack.
Ahah, found a good explanation from a pretty authoritative source:
http://groups.google.com/groups?oi=djq&selm=an_477899304
Nothing like getting it straight from the horse's mouth.
(Note for any non-native-english-speakers: that's an expression, I've never
seen Mr Nagle's mouth personally)
--
greg
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-interfaces@postgresql.org
Cc: gsstark@mit.edu, ljb220@mindspring.com, nandrews@investsystems.co.uk
Subject: Re: pgin.tcl pg_exec_prepared slow (was: Released...)
In-Reply-To: <873c44sia6.fsf@stark.xeocode.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