From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Martín Marqués <martin(at)2ndquadrant(dot)com> |
Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, pgsql-www(at)postgresql(dot)org |
Subject: | Re: Returning a memory issue when accessing an attachment from the mailing list |
Date: | 2020-04-03 00:26:59 |
Message-ID: | 13555.1585873619@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
=?UTF-8?B?TWFydMOtbiBNYXJxdcOpcw==?= <martin(at)2ndquadrant(dot)com> writes:
>> I downloaded the mbox file and it appears that the patch is in there. As
>> a workaround, if you download the mbox file and import it into your mail
>> client, you should be able to view and download it.
> I was able to read the patch from the git repository, as it was
> already committed in the master branch. I wanted to point out the
> issue in case there was something not working. Seems it was just an
> isolated issue with this attachment.
It's not an isolated issue: a patch I just posted at
https://www.postgresql.org/message-id/7653.1585869509@sss.pgh.pa.us
is having the same problem. If you click on the link embedded on
that page,
https://www.postgresql.org/message-id/attachment/109592/gin-fuzzy-search-limit-fix-2.patch
all you see is
<memory at 0x7fa950fcf1c8>
The cfbot is also seeing that, apparently. because it's complaining
about a malformed patch --- but the copy that came back to me from
the mailing list is fine.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Martín Marqués | 2020-04-03 00:59:27 | Re: Returning a memory issue when accessing an attachment from the mailing list |
Previous Message | Martín Marqués | 2020-04-02 23:18:59 | Re: Returning a memory issue when accessing an attachment from the mailing list |