Re: Returning a memory issue when accessing an attachment from the mailing list

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Martín Marqués <martin(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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-04 16:52:40
Message-ID: 20200404165240.GA13712@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Greetings,

* Andres Freund (andres(at)anarazel(dot)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

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Fujii Masao 2020-04-07 16:04:20 commit message
Previous Message Andres Freund 2020-04-03 01:19:29 Re: Returning a memory issue when accessing an attachment from the mailing list