What's changing: The Postgres source connector adds an optional snapshot_socket_timeout config field to control the idle timeout for snapshot connection sockets, previously hardcoded to 30 seconds.
High priority — existing docs are now inaccurate or incomplete
None identified.
For reviewer consideration — worth documenting
- New optional Postgres connection field
snapshot_socket_timeout (seconds, default 30) lets self-hosted users raise the snapshot-connection idle timeout to avoid it being killed mid-snapshot under storage backpressure. Belongs in configuration/powersync-service/self-hosted-instances.mdx (https://docs.powersync.com/configuration/powersync-service/self-hosted-instances), in the "Postgres connection options" accordion, alongside the existing heartbeat_interval_seconds field.
Source PR: powersync-ja/powersync-service#739 (merged 2026-08-19)
Filed automatically by Claude Code (claude-sonnet-5). A human must verify the scope, prepare the docs PR, and publish it only once this update has been released.
What's changing: The Postgres source connector adds an optional
snapshot_socket_timeoutconfig field to control the idle timeout for snapshot connection sockets, previously hardcoded to 30 seconds.High priority — existing docs are now inaccurate or incomplete
None identified.
For reviewer consideration — worth documenting
snapshot_socket_timeout(seconds, default 30) lets self-hosted users raise the snapshot-connection idle timeout to avoid it being killed mid-snapshot under storage backpressure. Belongs inconfiguration/powersync-service/self-hosted-instances.mdx(https://docs.powersync.com/configuration/powersync-service/self-hosted-instances), in the "Postgres connection options" accordion, alongside the existingheartbeat_interval_secondsfield.Source PR: powersync-ja/powersync-service#739 (merged 2026-08-19)
Filed automatically by Claude Code (
claude-sonnet-5). A human must verify the scope, prepare the docs PR, and publish it only once this update has been released.