Josh Berkus wrote: > Bruce, > > > OK, you have a runaway report. You want to stop it. Query cancel is > > only going to stop the current query, and once you do that the next > > query is fed in so there is no way to actually stop the report, > > especially if the report is not being run from the same machine as the > > server (you can't kill the report process). How do you stop it without > > SIGTERM? You don't want to shut down the postmaster. > > Hmmm ... but, at least in the case of my apps, killing the PG connection > wouldn't fix things. Most apps I work on are designed to detect connection > failure and reconnect. I suspect that most platforms that use connection > pooling are the same. So your case would only work if you actually blocked > all connections from that host -- not a capability we'd discussed.
I don't think most apps reconnect on disconnect, except maybe pooled connections where you don't expect your state to be stable between connections. Certainly most reports can't just reconnect and keep going. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
