| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: stress test for parallel workers |
| Date: | 2019-07-23 22:46:42 |
| Message-ID: | CA+hUKGKEryGUqk3_8C=6dBpN3jGmRArrTxgKX6dZ67GEN1eEKQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 24, 2019 at 10:42 AM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> On Wed, Jul 24, 2019 at 10:03:25AM +1200, Thomas Munro wrote:
> > On Wed, Jul 24, 2019 at 5:42 AM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> > > #2 0x000000000085ddff in errfinish (dummy=<value optimized out>) at elog.c:555
> > > edata = <value optimized out>
> >
> > If you have that core, it might be interesting to go to frame 2 and
> > print *edata or edata->saved_errno.
>
> As you saw..unless someone you know a trick, it's "optimized out".
How about something like this:
print errorData[errordata_stack_depth]
If you can't find errordata_stack_depth, maybe look at the whole array
and try to find the interesting bit?
--
Thomas Munro
https://enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikita Glukhov | 2019-07-23 22:48:26 | Re: Support for jsonpath .datetime() method |
| Previous Message | Justin Pryzby | 2019-07-23 22:42:55 | Re: stress test for parallel workers |