| 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 12:38:32 |
| Message-ID: | CAA4eK1Ld1fbROer6fY1BHUc=xWzpE1O3Ms3ZuRyWjLJGQ82P=g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
>
> Here is explain for this query:
> https://explain.depesz.com/s/slpM
>
> If i change any part of this query, like remove filter
> client_tt.id_client_tt or try it on other data set - it works
>
Can you share the plan after you change the query?
> For me it's looks like a bug (
Yeah.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next 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 |
| Previous Message | maxim.boguk | 2017-11-29 10:06:49 | BUG #14936: Huge backend memory usage during schema dump of database with many views |