pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Mircea Pirv <mircea@reva.tech>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16094: Database entering recovery mode
Date: Thu, 7 Nov 2019 11:35:51 +0900
Message-ID: <20191107023551.GG1768@paquier.xyz> (raw)
In-Reply-To: <CANpOcWB=5c4n_dveDeJanK0Y4cz+uCFdz0bW6Pyd40=Cf2qXfA@mail.gmail.com>
References: <16094-8fb7061e5370fb00@postgresql.org>
	<6649.1572879825@sss.pgh.pa.us>
	<CANpOcWB=5c4n_dveDeJanK0Y4cz+uCFdz0bW6Pyd40=Cf2qXfA@mail.gmail.com>

On Wed, Nov 06, 2019 at 03:37:31PM +0200, Mircea Pirv wrote:
> #2  WaitEventSetWait (set=0x55bc137a5948, timeout=<error reading variable:
> Cannot access memory at address 0x7ffee2d44ae0>, occurred_events=<error
> reading variable: Cannot access memory at address 0x7ffee2d44ad8>,
> nevents=<error reading variable: Cannot access memory at address
> 0x7ffee2d44afc>, wait_event_info=<optimized out>) at
> ./build/../src/backend/storage/ipc/latch.c:1032
>         rc = <optimized out>
>         returned_events = 0
>         start_time = <error reading variable start_time (Cannot access
> memory at address 0x7ffee2d44b00)>
>         cur_time = <error reading variable cur_time (Cannot access memory
> at address 0x7ffee2d44b10)>
>         cur_timeout = <error reading variable cur_timeout (Cannot access
> memory at address 0x7ffee2d44ae8)>
> Backtrace stopped: Cannot access memory at address 0x7ffee2d44b78

Is this the only part of the stack you can get?  WaitEventSetWait()
gets called in three places, which are be-secure.c, syslogger.c and
condition_variable.c.  Could it be possible to see more of the actual
callers here?
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (5+ messages)  latest in thread

Message-ID: <20191107023551.GG1768@paquier.xyz>
Permalink:  ../20191107023551.GG1768@paquier.xyz/
Also on:    postgresql.org/message-id/20191107023551.GG1768@paquier.xyz

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: michael@paquier.xyz, mircea@reva.tech, tgl@sss.pgh.pa.us
  Subject: Re: BUG #16094: Database entering recovery mode
  In-Reply-To: <20191107023551.GG1768@paquier.xyz>
  References: <16094-8fb7061e5370fb00@postgresql.org> <6649.1572879825@sss.pgh.pa.us> <CANpOcWB=5c4n_dveDeJanK0Y4cz+uCFdz0bW6Pyd40=Cf2qXfA@mail.gmail.com> <20191107023551.GG1768@paquier.xyz>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox