Hello Fedora, I installed a new Fedora release last week and ran into a peculiar problem:
Each night I need to run computations through about 70.000 rows and using PostgreSQL release 16.3 that took about 4 hours to complete, but using release 16.9 the same computations now take about 8 hours to complete. I've already submitted a bug report at bugzilla.redhat.com this morning about differences in pg_config that showed up, but I would also like to have a custom build in /usr/local. However, if I build postgresql-16.9 with ./configure --prefix=/usr/local; make -j32; make install, and modify the ExecStart in my drop-in accordingly, systemctl start postgresql does not exit at all. The journal tells me this: started from /usr/bin: Jul 20 11:21:21 r102.long4core.com systemd[1]: Starting postgresql.service - PostgreSQL database server... Jul 20 11:21:22 r102.long4core.com postgres[121322]: 2025-07-20 11:21:22 CEST [121322] LOG: redirecting log output to logging collector process Jul 20 11:21:23 r102.long4core.com systemd[1]: Started postgresql.service - PostgreSQL database server. Jul 20 11:21:23 r102.long4core.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=postgresql comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' started from /usr/local/bin: Jul 20 11:43:02 r102.long4core.com systemd[1]: Starting postgresql.service - PostgreSQL database server... Jul 20 11:43:03 r102.long4core.com postgres[123063]: 2025-07-20 11:43:03 CEST [123063] LOG: redirecting log output to logging collector process --- NOTHING --- Jul 20 11:43:24 r102.long4core.com systemd[1]: postgresql.service: Killing process 123065 (postgres) with signal SIGKILL. Jul 20 11:43:24 r102.long4core.com systemd[1]: postgresql.service: Deactivated successfully. Jul 20 11:43:24 r102.long4core.com systemd[1]: Stopped postgresql.service - PostgreSQL database server. Jul 20 11:43:24 r102.long4core.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=postgresql comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 20 11:43:24 r102.long4core.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=postgresql comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 20 11:43:24 r102.long4core.com systemd[1]: postgresql.service: Consumed 2.179s CPU time, 1.7G memory peak. The very first time I ran it, it seemed to work, but since then I'm not able to start postgres this way. Help would be appreciated :) Thanks, Mischa. -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
