Re: BUG in 10.1 - dsa_area could not attach to a segment that has been freed

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Alexander Voytsekhovskyy <young(dot)inbox(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)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 14:12:03
Message-ID: CAA4eK1JsYq=mK43GzaijFZF5zM_poSNZBodOed3Qordap0mUiA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Nov 29, 2017 at 6:58 PM, Alexander Voytsekhovskyy
<young(dot)inbox(at)gmail(dot)com> wrote:
>
>
> On Wed, Nov 29, 2017 at 2:38 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
> wrote:
>>
>> On Tue, Nov 28, 2017 at 10:47 PM, Alexander Voytsekhovskyy
>> <young(dot)inbox(at)gmail(dot)com> wrote:
>> > Hi,
>> >
>> > in very certain case i am getting error
>> >
>> > "ERROR: dsa_area could not attach to a segment that has been freed"
>> >
>>
>> Can you try to get call stack so that we can get a better picture of
>> what is happening here? One way could be you can change this ERROR to
>> PANIC which will generate core dump and you can get stack trace.
>>
>
> Yes, i can do both - i can reproduce it on test environment also
>
> is there somewhere manual for that?
>

You can get some information from the below link:
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-11-29 14:29:29 Re: [BUGS] Improper const-evaluation of HAVING with grouping sets and subquery pullup
Previous Message Alexander Voytsekhovskyy 2017-11-29 13:28:07 Re: BUG in 10.1 - dsa_area could not attach to a segment that has been freed