| From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
|---|---|
| To: | "Day, David" <dday(at)redcom(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: segmentation fault postgres 9.3.5 core dump perlu related ? |
| Date: | 2015-01-31 05:46:59 |
| Message-ID: | CAFaPBrSKoqnFyfu6hEVnNtVbMrHf+iSrxATX69CWeEajH7_xig@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jan 30, 2015 at 9:54 AM, Day, David <dday(at)redcom(dot)com> wrote:
>
> Alan,
>
>
>
> I tried as you suggested, I believe the gdb debugger is giving some false
> indication about threads.
>
> Whether I attach to a newly launched backend or a backend that has been
> executing the suspect perlu function.
>
> The “info threads” result is two. Suspiciously they are both at the same
> location.
>
>
>
Curious, hrm, well, assuming gdb isn't lying about threads-- I think that
would point an extension or a external library (shared_preload_libraries or
local_preload_libraries).
Does info threads on the postmaster also report threads?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leon Dang | 2015-01-31 08:08:36 | Re: Request for review of new redis-fdw module |
| Previous Message | Craig Ringer | 2015-01-31 00:28:20 | Re: trouble adding a node to BDR |