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

I see my fault

here is GDB with correct symbols

Program received signal SIGUSR1, User defined signal 1.
pagetable_insert (found=<synthetic pointer>, key=8192, tb=<optimized out>)
at
/build/postgresql-10-qAeTPy/postgresql-10-10.1/build/../src/include/lib/simplehash.h:540
540
/build/postgresql-10-qAeTPy/postgresql-10-10.1/build/../src/include/lib/simplehash.h:
No such file or directory.
Continuing.

Program received signal SIGUSR1, User defined signal 1.
pagetable_insert (found=<synthetic pointer>, key=8192, tb=<optimized out>)
at
/build/postgresql-10-qAeTPy/postgresql-10-10.1/build/../src/include/lib/simplehash.h:540
540 in
/build/postgresql-10-qAeTPy/postgresql-10-10.1/build/../src/include/lib/simplehash.h
Continuing.

Program received signal SIGUSR1, User defined signal 1.
0x0000556024ed08ee in slot_deform_tuple (slot=slot(at)entry=0x556026638e60,
natts=natts(at)entry=29) at
/build/postgresql-10-qAeTPy/postgresql-10-10.1/build/../src/backend/access/common/heaptuple.c:1073
1073
/build/postgresql-10-qAeTPy/postgresql-10-10.1/build/../src/backend/access/common/heaptuple.c:
No such file or directory.
Continuing.

Program received signal SIGUSR1, User defined signal 1.
0x0000556024ed08ee in slot_deform_tuple (slot=slot(at)entry=0x556026638e60,
natts=natts(at)entry=29) at
/build/postgresql-10-qAeTPy/postgresql-10-10.1/build/../src/backend/access/common/heaptuple.c:1073
1073 in
/build/postgresql-10-qAeTPy/postgresql-10-10.1/build/../src/backend/access/common/heaptuple.c
Continuing.

Program received signal SIGUSR1, User defined signal 1.
0x00007f53e538e9b3 in __epoll_wait_nocancel () at
../sysdeps/unix/syscall-template.S:84
84 ../sysdeps/unix/syscall-template.S: No such file or directory.
Continuing.

Program received signal SIGUSR1, User defined signal 1.
0x00007f53e538e9b3 in __epoll_wait_nocancel () at
../sysdeps/unix/syscall-template.S:84
84 in ../sysdeps/unix/syscall-template.S
Continuing.

Program received signal SIGUSR1, User defined signal 1.
0x00005560250a0c4f in pagetable_insert (found=<synthetic pointer>,
key=14592, tb=0x556026699df0) at
/build/postgresql-10-qAeTPy/postgresql-10-10.1/build/../src/include/lib/simplehash.h:493
493
/build/postgresql-10-qAeTPy/postgresql-10-10.1/build/../src/include/lib/simplehash.h:
No such file or directory.
Detaching from program: /usr/lib/postgresql/10/bin/postgres, process 7453

On Wed, Nov 29, 2017 at 4:12 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
wrote:

> 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
>