Re: what is up with the PG mailing lists?
От | Magnus Hagander |
---|---|
Тема | Re: what is up with the PG mailing lists? |
Дата | |
Msg-id | 472A4A86.6000307@hagander.net обсуждение исходный текст |
Ответ на | Re: what is up with the PG mailing lists? (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-www |
Tom Lane wrote: > Magnus Hagander <magnus@hagander.net> writes: >> Oh, and the headers I sent were because the email was stuck in the >> moderation queue. > > Yeah --- one of the worst problems in diagnosing this is that there's > no way for anyone except the moderator to know if a delay was simply > waiting-for-moderation or if it indicates an actual system problem. > > What are the chances of getting something into the headers to indicate > whether a message was delayed by moderation? Not sure - Marc? You're the one who know majordomo... Anyway, I just ran a script on all the mail sitting in my mailbox from postgresql mailinglists delivered in the past two hours. It's a total of 22 mails (should be more, I know - but I need to deal with differences in date before I get there, this is a first rough cut of the script). Here's the top lines from the query: select path,count(*),avg(t)::int from data group by path order by 2 desc,3 desc; on this data. Basically, it's the paths that appear often, and the average delivery time between them (in seconds). I've only included paths that appear 7 or more times, plus the two rows for mails posted by Tom and me (there are others that appear twice as well, but I'm not including those). This is all delivery to me, which is why the path mx2.hub.org->svr2.hagander.net and svr2.hagander.net->svr2.hagander.net (my antispam) is included. path | count | avg ---------------------------------------------------------------------------------------+-------+------ postgresql.org -> mx2.hub.org | 22 | 57 svr2.hagander.net -> svr2.hagander.net | 22 | 1 mx2.hub.org -> svr2.hagander.net | 22 | 1 postgresql.org -> localhost (mx1.hub.org [200.46.204.184]) | 15 | 3335 localhost (mx1.hub.org [200.46.204.184]) -> postgresql.org | 15 | 23 postgresql.org -> localhost (mx1.hub.org [200.46.204.183]) | 7 | 2710 localhost (mx1.hub.org [200.46.204.183]) -> postgresql.org | 7 | 17 sss.pgh.pa.us (8.14.1/8.14.1) -> postgresql.org | 3 | 8 svr2.hagander.net -> postgresql.org | 2 | 2 (sorry about the breakup of the table, it's the long lines for mx1.hub.org. Table attached as well for easier reading) To me this clearly shows that mail is backed up between postgresql.org (this is svr1, if I'm not mistaken) and mx1.hub.org - which has two different IPs, but claims to be localhost (that can't be right, can it?). FYI, the count measures the difference in time between the Received: lines in the header. It's not fool-proof, but it works on all the paths inside hub.org and from there to my machine - it misses some originating MUAs (it's missed 2 out of the 22 emails parsed here) //Magnus path | count | avg ---------------------------------------------------------------------------------------+-------+------ postgresql.org -> mx2.hub.org | 22 | 57 svr2.hagander.net -> svr2.hagander.net | 22 | 1 mx2.hub.org -> svr2.hagander.net | 22 | 1 postgresql.org -> localhost (mx1.hub.org [200.46.204.184]) | 15 | 3335 localhost (mx1.hub.org [200.46.204.184]) -> postgresql.org | 15 | 23 postgresql.org -> localhost (mx1.hub.org [200.46.204.183]) | 7 | 2710 localhost (mx1.hub.org [200.46.204.183]) -> postgresql.org | 7 | 17 sss.pgh.pa.us (8.14.1/8.14.1) -> postgresql.org | 3 | 8 svr2.hagander.net -> postgresql.org | 2 | 2
В списке pgsql-www по дате отправления: