On Tue, 18 Jul 2006, Bruce Momjian wrote:
Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
http://archives.postgresql.org/pgsql-www/2006-07/msg00061.php
Yeah. I think the TODO item is intended to point to what is now
http://archives.postgresql.org/pgsql-hackers/2006-02/msg00163.php
or one of the earlier messages in that thread.
This is a very ugly problem. Note that there are also URLs that cannot
be changed, such as older messages that point to archive posts, and
many places on the web outside of our control.
Why can't we just write a script that creates new numbers as needed,
such as msg00163.1.php and msg00163.2.php? As far as I can tell, there
is nothing magical about the naming schema itself that would cause
such URLs to break anything.
Agreed. It is nice to have the emails numbered in arrival order, but
changes to old URLs are worse.
'k, so is the concensus here that I regenerate everything with the 'broken
msg seperator', and then revert to the unbroken one for new stuff? its no
sweat, I just fear this is going to re-crop up sometime in the future if
we ever have to regenerate from the mbox files, as well have some in
'broken format' and some in the 'unbroken', but renumbering *then* will
still affect everything ...
Basically, we're just differing the headaches to a later date when we have
no choice :(
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED]
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
