Hello, Listening to SIGPIPE could also help detecting "unclean" client-side connection aborts, e. G. due to a program crash or sigkill on the client, or network problem between server and client.
This way, the server could abort long-running statements immediately, instead of running them just to rollback them afterwards because the client does not commit. During development, I often forcedly abort my java clients, but the server continues to execute the current statement. Having two or three such sequential scans running in the background, selectively sending SIGTERM to the backends as root is the only way to get the postmaster responsive again. Thanks, Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
signature.asc
Description: OpenPGP digital signature
