Re: Not ready for 8.3

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
Cc: Dave Page <dpage(at)postgresql(dot)org>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Not ready for 8.3
Date: 2007-05-17 07:32:27
Message-ID: 464C050B.1080902@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim C. Nasby wrote:
> On Wed, May 16, 2007 at 07:48:10PM +0200, Magnus Hagander wrote:
>> Dave Page wrote:
>>>>> I the current URLs represent the month, and the ID of the message as
>>>>> it comes out of the mbox I believe. We could probably write a script
>>>>> to dump a list of message IDs, directories and mbox positions I
>>>>> imagine, and then import that into a new database.
>>>>
>>>> Yeah, if the files still resemble real emails then we can probably come
>>>> up with a way to pull the data in.
>>> We have all the mbox files, so we can import them from there as raw
>>> messages.
>> yeah, that's clearly the best source to work from. It's *possible* work
>> from the mhonarc files (I've done it before), but it's more work.
>
> We'd want the old URLs to be redirected too, so at some point we'll have
> to deal with mhonarc.

Right. Grabbing the msgid alone from them shouldn't be too hard though.
It's included in the "meta-headers" mhonarc sticks in each file, so it
should be a simple regex to find it.

//Magnus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2007-05-17 07:53:22 Re: Lack of urgency in 8.3 reviewing
Previous Message Alvaro Herrera 2007-05-17 04:25:42 Re: BufFileWrite across MAX_PHYSICAL_FILESIZE boundary