| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Reinitialize stack base after fork (for the benefit of rr)? |
| Date: | 2020-04-06 04:40:34 |
| Message-ID: | CAH2-WzkvKg0v_K7BQ3URBLAre1pDa5stfkYzxVfnhD3fF4v6+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Apr 5, 2020 at 8:56 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Perhaps put it on a wiki page?
I added a new major section to the "getting a stack trace" wiki page:
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-04-06 05:03:32 | SyncRepLock acquired exclusively in default configuration |
| Previous Message | Dilip Kumar | 2020-04-06 04:26:02 | Re: Index Skip Scan |