Date: Wed, 26 Mar 2008 10:54:46 -0300
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: NikhilS <nikkhils@gmail.com>, pgsql-patches@postgresql.org
Subject: Re: Auto Partitioning Patch - WIP version 1
Message-ID: <20080326135446.GD8100@alvh.no-ip.org>
References: <20080326134202.GB8100@alvh.no-ip.org>
	<200803261348.m2QDme903600@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200803261348.m2QDme903600@momjian.us>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)

Bruce Momjian escribió:
> Alvaro Herrera wrote:

> > My point is that you should only _add_ Message-Ids, not remove them.
> > You can move the messages from one queue to the other to your heart's
> > content, but the Message-Id URL should continue to work with no changes.
> 
> Well, when an email is applied, it is deleted.  How do I update the
> message-id for that in an automated manner.  Right now a rebuild deleted
> all the links and recreates them.

Well, remove the part that deletes links, and keep the part that
creates links.  That way, links that used to work continue working.

I am assuming you use hard links -- obviously this doesn't work with
symlinks.  (My script creates hard links.)

> > after the name of the poster, so that it would be visible on the index
> > page and the user didn't have to open the page to get it.
> 
> We can do that if people want.  I used to show the message id on the
> thread page but several felt it was too cluttered-looking.

Well, it would have helped me.  I suggested "permalink" as text because
it is less clutter than the full Message-Id.  Besides, the Message-Id by
itself is useless, whereas a link is useful.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.