| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
| Cc: | Alexander Kukushkin <cyberdemn(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15346: Replica fails to start after the crash |
| Date: | 2018-08-22 17:50:34 |
| Message-ID: | 20180822175034.lnvwk5js32k6mjyz@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 2018-Aug-22, Dmitry Dolgov wrote:
> > ENOTIME for a closer look ATM, though, sorry. Maybe you could try
> > running under valgrind?
>
> Could you elaborate please, what can we find using valgrind in this case, some
> memory leaks? In any way there is a chance that everything will be ok, since
> even just a slow tracing under gdb leads to disappearing of this race
> condition.
I don't know. I was thinking it could detect some invalid write in
shared memory.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-08-23 04:14:20 | Re: BUG #15346: Replica fails to start after the crash |
| Previous Message | Dmitry Dolgov | 2018-08-22 15:42:16 | Re: BUG #15346: Replica fails to start after the crash |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2018-08-22 17:51:12 | Sv: Re: Query is over 2x slower with jit=on |
| Previous Message | Vladimir Sitnikov | 2018-08-22 17:21:32 | Re: Stored procedures and out parameters |