Segmentation fault in version 1.6.7

[rblst]

We want to use pg_cron version 1.6.7 in PostgreSQL 17, Rocky Linux 9.7.

The background worker "pg_cron launcher" suffers segmentation fault and crashes the server.

It does not matter if we go with background workers or localhost connections mode.

Here is an excerpt from the debug level logs:

2026-01-21 14:49:05.798 CET [4179112]: [75] LOG: database system is ready to accept connections
2026-01-21 14:49:05.808 CET [4179119]: [8] LOG: pg_cron scheduler started
2026-01-21 14:49:05.814 CET [4179112]: [76] DEBUG: reaping dead processes
2026-01-21 14:49:05.814 CET [4179112]: [77] LOG: background worker "pg_cron launcher" (PID 4179119) was terminated by signal 11: Segmentation fault
2026-01-21 14:49:05.814 CET [4179112]: [78] LOG: terminating any other active server processes
2026-01-21 14:49:05.814 CET [4179112]: [78] LOG: terminating any other active server processes
2026-01-21 14:49:05.814 CET [4179112]: [79] DEBUG: sending SIGQUIT to process 4179120
2026-01-21 14:49:05.815 CET [4179112]: [80] DEBUG: sending SIGQUIT to process 4179115
2026-01-21 14:49:05.815 CET [4179112]: [81] DEBUG: sending SIGQUIT to process 4179114
2026-01-21 14:49:05.815 CET [4179112]: [82] DEBUG: sending SIGQUIT to process 4179117
2026-01-21 14:49:05.815 CET [4179112]: [83] DEBUG: sending SIGQUIT to process 4179118
2026-01-21 14:49:05.816 CET [4179112]: [84] DEBUG: reaping dead processes
2026-01-21 14:49:05.817 CET [4179112]: [85] DEBUG: reaping dead processes
2026-01-21 14:49:05.817 CET [4179112]: [86] LOG: all server processes terminated; reinitializing

Version strings:

PostgreSQL 17.7 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11), 64-bit

$ dnf info pg_cron_17
Installed Packages
Name : pg_cron_17
Version : 1.6.7
Release : 1PGDG.rhel9
Architecture : x86_64
Size : 102 k
Source : pg_cron_17-1.6.7-1PGDG.rhel9.src.rpm

[rblst]

We've tried reverting to v1.6.5, it crashes the server with use_background_workers = on, but works with connections mode.

As a workaround, we've reverted to v1.6.4, it works with background workers too.