| 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:40:16 |
| Message-ID: | CA+hUKGLPaVKj9CXyWueq7Vt6yeS7_3VKRoMXVeWdYzScpjnD3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 24, 2019 at 10:03 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> > 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. ...
Rats. We already saw that it's optimised out so unless we can find
that somewhere else in a variable that's present in the core, we
probably can't find out what the operating system said. So my other
idea for getting this information next time is to try putting the
PostgreSQL logs somewhere that's more likely to be still working when
that thing fails.
--
Thomas Munro
https://enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2019-07-23 22:42:55 | Re: stress test for parallel workers |
| Previous Message | Alvaro Herrera | 2019-07-23 22:32:50 | Re: range_agg |