<div dir="ltr"><div class="gmail_quote">On Sat, Oct 9, 2010 at 3:30 PM, Dimitri Fontaine <span dir="ltr"><<a
href="mailto:dimitri@2ndquadrant.fr">dimitri@2ndquadrant.fr</a>></span>wrote:<br /><blockquote class="gmail_quote"
style="margin:0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Andrew Dunstan <<a
href="mailto:andrew@dunslane.net">andrew@dunslane.net</a>>writes:<br /> > I wish we could get the archive
processorto provide access to the<br /> > attachments even if they have a MIME type of text/whatever. That's a<br />
>horrid inefficiency. Maybe we could restrict it to text attachments<br /> > that have a Content-Type with a name
attributethat contains the<br /> > string 'patch', or a similar Content-Disposition filename attribute.<br /><br />
Iwish our super admins would have some time to resume the work on the<br /> new archives infrastructure, that was about
readyfor integration if not<br /> prime time:<br /><br /> <a
href="http://archives.beccati.org/pgsql-hackers/message/276290"
target="_blank">http://archives.beccati.org/pgsql-hackers/message/276290</a><br/><br /> As you see it doesn't suffer
fromthis problem, the threading is not<br /> split arbitrarily, and less obvious but it runs from a PostgreSQL<br />
database.Yes, that means the threading code is exercising our recursive<br /> querying facility, as far as I understand
it.<br/><br /></blockquote></div><br clear="all" />Something looks wrong with that thread. The message text in my mails
ismissing. Perhaps that is contained in the .bin files but I can't tell as the link leads to 404 Not Found.<br /><br
/>Regards,<br/>-- <br />gurjeet.singh<br />@ EnterpriseDB - The Enterprise Postgres Company<br /><a
href="http://www.EnterpriseDB.com">http://www.EnterpriseDB.com</a><br/><br />singh.gurjeet@{ gmail | yahoo }.com<br
/>Twitter/Skype:singh_gurjeet<br /><br />Mail sent from my BlackLaptop device<br /></div>