invalid message size 327696859971 in shared memory queue
- Dominant language
- C
- Stars
- 3.9k
- Forks
- 260
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
pg_cron launcher got crashed in ERROR: invalid message size and restart again successfully,
Postgresql v13.6 , pg_cron
2023-03-24 07:45:45.121 UTC::@:[2698016]:[38344-1]:LOG: cron job 1 COMMAND completed: CALL
2023-03-24 07:45:45.122 UTC::@:[2698016]:[38345-1]:LOG: cron job 3 COMMAND completed: CALL
2023-03-24 07:45:45.122 UTC::@:[2698016]:[38346-1]:ERROR: invalid message size 327696859971 in shared memory queue
2023-03-24 07:45:45.126 UTC::@:[3596697]:[49-1]:LOG: background worker "pg_cron launcher" (PID 2698016) exited with exit code 1
2023-03-24 07:45:46.173 UTC::@:[2312201]:[1-1]:LOG: pg_cron scheduler started
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by investigating the pg_cron launcher and its shared memory queue around the reported invalid message size, using the PostgreSQL 13.6 log sequence as the reproduction context. Determine why the launcher exits and restarts, then add coverage or a documented verification that the queue error no longer crashes the launcher.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100