Date: Fri, 25 Jan 2013 15:46:59 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Heikki Linnakangas <hlinnakangas@vmware.com>
Cc: pgsql-www@postgresql.org
Subject: Re: Attachment doesn't open in new archive
Message-ID: <20130125184659.GG5584@alvh.no-ip.org>
References: <5102BCBC.40701@vmware.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <5102BCBC.40701@vmware.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org

Heikki Linnakangas wrote:
> I cannot download the attachment in this message:
>=20
> http://www.postgresql.org/message-id/5090F05D.5060507@wulczer.org
>=20
> All I get is a zero-length file.

Weird.  It's a zero-length file in the old archives as well.  The MIME
headers of that attachment are pretty funny:

Content-Type: text/x-diff;
 name=3D"0001-Set-SQL-error-code-for-SPI-errors-raised-from-userla.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename*0=3D"0001-Set-SQL-error-code-for-SPI-errors-raised-from-userla.pa=
";
 filename*1=3D"tch"

Note the "filename*N" thingy.  I had never seen this.  I wonder if this
is what's causing the parsers to fail.

--=20
=C1lvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


--=20
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www