public inbox for [email protected]
help / color / mirror / Atom feedFrom: Joshua D. Drake <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: Andrew Sullivan <[email protected]>
Cc: [email protected]
Subject: Re: what is up with the PG mailing lists?
Date: Thu, 1 Nov 2007 08:47:52 -0700
Message-ID: <20071101084752.64ac3936@scratch> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<20071101080959.49f3087b@scratch>
<[email protected]>
<[email protected]>
On Thu, 01 Nov 2007 16:30:13 +0100
Magnus Hagander <[email protected]> wrote:
> > 1. All the mail RFCs are totally clear that latency is to be
> > expected in the mail system. Every time I hear complaints about
> > mail latency that entails delays of merely hours, I worry that
> > people are treating SMTP as though it's XMPP. It ain't, and it's
> > designed _not_ to be.
>
> There's a difference between acceptable delay and what we're often
> getting. Sure, SMTP should have latency. But a modern SMTP system
> shouldn't take hours to deliver an email.
Exactly. It is pretty silly to think that a modern, well engineered
system will take hours to deliver mail. It is like people have just
been brow beaten into accepting the poor performance of the lists.
There are exception of course... I run into Exchange not really likely
greylisting for example.
> > 2. There are plenty of individual relays involved here, and
> > saying "it's slow" without mail headers is no more helpful in
> > demystifying mail issues than are posts to -performance without
> > EXPLAIN ANALYSE output.
>
> Sure. But I can tell you that *every single time* I've looked at
> latencies, the problem has been at postgresql.org or hub.org. And in
> my own case, there is just one relay on the way, usually with a
> latency of <5 seconds.
>
This is also the case with me and I just gave up because nobody
actually seems to care about how bad the performance really is.
> >> It would be great if the actual sysadmin team had management
> >> ability on the mail servers.
> >
> > This seems true to me. More important,
> >
> >> Note we still don't have documentation on this stuff
> >
> > I think this is a very serious problem. Some of the issues have
> > been perplexing to diagnose because of the poor documentation. We
> > talked about this most recently with respect to MX records and
> > higher-preference-number MXes having the user list from the final
> > destination, so that we could generate rejects consistently, IIRC.
>
> Can't agree more.
>
I wish -core actually realized how good it could be.
Thousands of people rely on these lists. We advertise them as the form
of community support. They are, outside of the code our most important
feature that we provide to our community. Yet...
Sincerely,
Joshua D. Drake
> //Magnus
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 1: if posting/reading
> through Usenet, please send an appropriate subscribe-nomail command
> to [email protected] so that your message can get through to
> the mailing list cleanly
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
Attachments:
[application/pgp-signature] signature.asc (189B, 2-signature.asc)
download
view thread (59+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: what is up with the PG mailing lists?
In-Reply-To: <20071101084752.64ac3936@scratch>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox