On 2019-Jul-14, Tom Lane wrote:
> Magnus Hagander <magnus@hagander.net> writes:
> > This means that instead of being:
> > https://www.postgresql.org/message-id/CABUevEyqGVV-s1yXQBsTpoPDCHy79j-yDtJcucrPb9Hh4CFTNg%40mail.gmail.com
> > The url would be:
> > https://www.postgresql.org/message-id/Z0oaTfo56bV4tke6-r_PKJstHF8=
>
> FWIW, I don't care for that one bit. Yeah, message IDs are pretty
> opaque in many cases, but at least they're not designed and built to
> be opaque. An example of what would be lost is the ability to find
> a message given one of these URLs in any other archive, such as one's
> personal mail archive. (Unless one sets up a mapping table to match
> this transform, which would be a big PITA.)
+1
> > Any access to the old message-id based URLs would automatically receive a
> > permanent redirect to the new ones.
>
> If you remove the ability to find a message in the archive from its
> original message ID, I will be REALLY unhappy, because that will break
> lookups in the other direction (ie, given a message in my local files,
> go find it --- and its thread --- in the PG archives).
Me too.
> On the whole I don't see any good reason to change this.
+1
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services