Re: stress test for parallel workers
От | Thomas Munro |
---|---|
Тема | Re: stress test for parallel workers |
Дата | |
Msg-id | CA+hUKGKEryGUqk3_8C=6dBpN3jGmRArrTxgKX6dZ67GEN1eEKQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: stress test for parallel workers (Justin Pryzby <pryzby@telsasoft.com>) |
Ответы |
Re: stress test for parallel workers
|
Список | pgsql-hackers |
On Wed, Jul 24, 2019 at 10:42 AM Justin Pryzby <pryzby@telsasoft.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@telsasoft.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
В списке pgsql-hackers по дате отправления: