Greetings,
* Andres Freund (andres@anarazel.de) wrote:
> On 2020-04-02 21:59:27 -0300, Martín Marqués wrote:
> > > 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
>
> If I had to guess the "<memory at 0x7fa950fcf1c8>" is caused by part of
> the stack having been upgraded/downgraded. With the memoryview type not
> being recognized with whatever is supposed to write out the data.
>
> > Looks like t I'm able to download this patch perfectly.
>
> Did you check whether the contents are correct? It downloads for me, but
> it contains "<memory at 0x7fa950fcf1c8>".
For the archives sake, just wanted to mention that this has been
resolved. If you see anything like this again, please don't hesitate to
reach out.
Thanks,
Stephen