From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Alexander Voytsekhovskyy <young(dot)inbox(at)gmail(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG in 10.1 - dsa_area could not attach to a segment that has been freed |
Date: | 2017-11-29 00:04:34 |
Message-ID: | CAEepm=3b=Y8YMW1-6dZyUUi4quWVKcObNv1ROBosBEi_uQ96gw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Nov 29, 2017 at 12:18 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Wed, Nov 29, 2017 at 2:17 AM, Alexander Voytsekhovskyy
> <young(dot)inbox(at)gmail(dot)com> wrote:
>> in very certain case i am getting error
>>
>> "ERROR: dsa_area could not attach to a segment that has been freed"
>
> You are likely seeing the same problem as discussed here:
> https://www.postgresql.org/message-id/15e84857859.d4f2ff2b8299.3910523281971861294@zohocorp.com
Hmm. Well, it's the same error message but I don't think it's the
same: that other thread was about C extension code using APIs
incorrectly. This is parallel query, which shouldn't reach that error
unless all the backends detach before one backend tries to attach,
which I wouldn't normally expect to happen unless something else went
wrong first. Then Alexander would presumably have also seen another
error message too but he didn't say that. So I'm not yet sure how
this condition is being reached.
--
Thomas Munro
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-11-29 00:33:30 | Re: BUG in 10.1 - dsa_area could not attach to a segment that has been freed |
Previous Message | Michael Paquier | 2017-11-28 23:18:10 | Re: BUG in 10.1 - dsa_area could not attach to a segment that has been freed |