> > Right. For this purpose, pgpool sends param packet to client > > periodically while waiting for a reply from backend to detect if the > > connection to the client is broken. If it's broken, pgool sends cancel > > packet to backend not to waste backend machine's CPU cycle. > > The downside to this is that it will cause spurious failures for > transient network failures even if the network comes back before it's > actually needed.
Can't we expect such a transient error to be fixed by underlying TCP/IP stack? -- Tatsuo Ishii SRA OSS, Inc. Japan -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
