From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | archives, attachments, etc (was: Patch to add a primary key using an existing index) |
Date: | 2010-10-09 19:30:19 |
Message-ID: | m2eibzf9kk.fsf_-_@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I wish we could get the archive processor to provide access to the
> attachments even if they have a MIME type of text/whatever. That's a
> horrid inefficiency. Maybe we could restrict it to text attachments
> that have a Content-Type with a name attribute that contains the
> string 'patch', or a similar Content-Disposition filename attribute.
I wish our super admins would have some time to resume the work on the
new archives infrastructure, that was about ready for integration if not
prime time:
http://archives.beccati.org/pgsql-hackers/message/276290
As you see it doesn't suffer from this problem, the threading is not
split arbitrarily, and less obvious but it runs from a PostgreSQL
database. Yes, that means the threading code is exercising our recursive
querying facility, as far as I understand it.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Gurjeet Singh | 2010-10-09 20:54:47 | Re: archives, attachments, etc (was: Patch to add a primary key using an existing index) |
Previous Message | Andrew Dunstan | 2010-10-09 18:46:20 | Re: Patch to add a primary key using an existing index |