| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | L J Bayuk <ljb220(at)mindspring(dot)com> |
| Cc: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>, pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: pgin.tcl pg_exec_prepared slow (was: Released...) |
| Date: | 2004-07-07 01:44:17 |
| Message-ID: | 873c44sia6.fsf@stark.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
L J Bayuk <ljb220(at)mindspring(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomasz Myrta | 2004-07-07 07:05:20 | Re: Libpq and transactions |
| Previous Message | Greg Stark | 2004-07-07 01:27:45 | Re: pgin.tcl pg_exec_prepared slow (was: Released...) |