Re: Reinitialize stack base after fork (for the benefit of rr)? - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Reinitialize stack base after fork (for the benefit of rr)?
Date
Msg-id CAH2-WzkvKg0v_K7BQ3URBLAre1pDa5stfkYzxVfnhD3fF4v6+Q@mail.gmail.com
Whole thread Raw
In response to Re: Reinitialize stack base after fork (for the benefit of rr)?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Sun, Apr 5, 2020 at 8:56 PM Andres Freund <andres@anarazel.de> wrote:
> Perhaps put it on a wiki page?

I added a new major section to the "getting a stack trace" wiki page:


https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD#Recording_Postgres_using_rr_Record_and_Replay_Framework

Feel free to add to and edit this section yourself.

> Were you doing this because of occasional failures in autovacuum
> workers?  If so, that shouldn't be necessary after the stack base change
> (previously workers IIRC also could start with the wrong stack base -
> but didn't end up checking stack depth except for expression indexes).

No, just a personal preference for things like this.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Index Skip Scan
Next
From: Andres Freund
Date:
Subject: SyncRepLock acquired exclusively in default configuration