Re: Not ready for 8.3

From: Aidan Van Dyk <aidan(at)highrise(dot)ca>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: magnus(at)hagander(dot)net, stefan(at)kaltenbrunner(dot)cc, alvherre(at)commandprompt(dot)com, jd(at)commandprompt(dot)com, bruce(at)momjian(dot)us, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Not ready for 8.3
Date: 2007-05-16 14:19:44
Message-ID: 20070516141944.GL9991@yugib.highrise.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Tatsuo Ishii <ishii(at)postgresql(dot)org> [070516 07:23]:

> Maybe. However I think "subject-sequence" has some advantages over
> Message-Id:
>
> - Easy to identify. Message-Id may not appear on some MUA with default
> setting
>
> - More handy than lengthy message Id
>
> - Easy to detect messages not delivered, by knowing that the sequence
> number was skipped

IMNSHO, we should be encouraging lists to move *away* from subject
munging. Adding more characters into a subject line which can already
be quite long is just making the situation worse.

And of course, once you realize that subject munging is wrong, putting
the "list-sequence" into a header of no real value, unless you believe
your MTA/MUA filtering to be somehow dropping list messages, and your
sequence numbers will prove to you if that's true or not. Oh - but
wait, don't we all, as PostgreSQL users realize that sequences aren't
generally guaranteed to be gapless anyways (sure, there are work
"solutions", but I'm not about to audit any MTA/list software for
that...)

;-)

--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message tomas 2007-05-16 14:29:41 Re: Not ready for 8.3
Previous Message Alvaro Herrera 2007-05-16 14:06:02 Re: Not ready for 8.3