| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Andreas Seltenreich <seltenreich(at)gmx(dot)de> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader |
| Date: | 2016-04-30 07:01:07 |
| Message-ID: | CAA4eK1Jtuo9JiJsDD=rZuSDk4OfExjCzS_Lz6NB8Oj3O8TanDA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Apr 30, 2016 at 5:58 AM, Andreas Seltenreich <seltenreich(at)gmx(dot)de>
wrote:
>
> Alvaro Herrera writes:
> > Amit Kapila wrote:
> >> It will be helpful if you can find the offending query or plan
> >> corresponding to it?
> >
> > So I suppose the PID of the process starting the workers should be in
> > the stack somewhere.
>
> Ja, it's right on the top, but long gone by now…
>
> > With that one should be able to attach to that process and get another
> > stack trace. I'm curious on whether you would need to have started
> > the server with "postgres -T"
>
> This sounds like it should work to capture more context when the
> Assertion fails the next time.
>
Sounds good. So can we assume that you will try to get us the new report
with more information?
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | zeray87 | 2016-04-30 07:11:16 | Windows 7, Visual Studio 2010: building PgAdmin3 |
| Previous Message | Amit Kapila | 2016-04-30 06:58:43 | Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader |