| From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | Sushrut Shivaswamy <sushrut(dot)shivaswamy(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Background Processes in Postgres Extension |
| Date: | 2024-04-29 03:43:54 |
| Message-ID: | CAExHW5vYrn9To5nDXFM_vvHUjzxBrezYkOKiG1jDTB44f15yxg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Apr 27, 2024 at 9:26 PM Sushrut Shivaswamy <
sushrut(dot)shivaswamy(at)gmail(dot)com> wrote:
> Thanks for the suggestion on using postgres background worker.
>
> I tried creating one following the implementation in worker_spi and am
> able to spawn a background worker successfully.
>
> However, the background worker seems to cause postmaster to crash when I
> wait for it to finish using `WaitForBackgroundWorkerShutdown.
> The function called by the background worker is empty except for logging a
> message to disk.
>
When debugging a crash, backtrace from core dump is useful. if you can
reproduce the crash, running reproduction with gdb attached to a process
intended to crash is more useful.
--
Best Wishes,
Ashutosh Bapat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2024-04-29 04:03:28 | Re: Introduce XID age and inactive timeout based replication slot invalidation |
| Previous Message | vignesh C | 2024-04-29 03:29:09 | Re: New committers: Melanie Plageman, Richard Guo |