What happened
The DEB package currently includes pg_hardstorage.service and pg_hardstorage@.service for the pg_hardstorage agent, but it does not provide a unit file for pg_hardstorage wal stream.The ExecStart lines of pg_hardstorage.service and pg_hardstorage@.service are as follows:
ExecStart=/usr/bin/pg_hardstorage agent
However, multiple sections of the documentation seem to describe pg_hardstorage.service as being used to perform the pg_hardstorage wal stream function. For example:
"Tutorials" -> "2.4 Start the WAL streamer (this is the always-on core)" https://docs.pghardstorage.org/tutorials/getting-started/#24-start-the-wal-streamer-this-is-the-always-on-core:
The stream is gap-free across agent restarts. Supervise it with systemd (the package ships pg_hardstorage@<deployment>.service for exactly this) or your container scheduler.
"R1 - Repo region gone" -> "Stop the streamer so PG isn't blocked indefinitely." https://docs.pghardstorage.org/reference/runbooks/R1-repo-region-gone/#procedure :
systemctl stop pg_hardstorage
# or send SIGTERM to the wal stream process
So, does pg_hardstorage.service serve both the agent and WAL streaming functions, or is another systemd unit file provided specifically for pg_hardstorage wal stream?
To reproduce
pg_hardstorage version
pg_hardstorage 1.3.5 (3ac1c37, built 2026-09-01T09:09:57Z)
Doctor report
N/A
Logs
N/A
Environment
- OS: Debian 12.15
- Architecture: amd64
- PG: 18.6
- Repo backend: fs
- Coordination: single-host
Anything else
What happened
The DEB package currently includes
pg_hardstorage.serviceandpg_hardstorage@.servicefor the pg_hardstorage agent, but it does not provide a unit file for pg_hardstorage wal stream.The ExecStart lines of pg_hardstorage.service and pg_hardstorage@.service are as follows:ExecStart=/usr/bin/pg_hardstorage agentHowever, multiple sections of the documentation seem to describe pg_hardstorage.service as being used to perform the pg_hardstorage wal stream function. For example:
"Tutorials" -> "2.4 Start the WAL streamer (this is the always-on core)" https://docs.pghardstorage.org/tutorials/getting-started/#24-start-the-wal-streamer-this-is-the-always-on-core:
The stream is gap-free across agent restarts. Supervise it with systemd (the package ships pg_hardstorage@<deployment>.service for exactly this) or your container scheduler."R1 - Repo region gone" -> "Stop the streamer so PG isn't blocked indefinitely." https://docs.pghardstorage.org/reference/runbooks/R1-repo-region-gone/#procedure :
So, does pg_hardstorage.service serve both the agent and WAL streaming functions, or is another systemd unit file provided specifically for pg_hardstorage wal stream?
To reproduce
pg_hardstorage version
pg_hardstorage 1.3.5 (3ac1c37, built 2026-09-01T09:09:57Z)
Doctor report
N/A
Logs
N/A
Environment
Anything else