vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| The cancel function is implemented. See http://developer.postgresql.org/docs...min.html#FUNCT IONS-ADMIN-SIGNAL-TABLE. Kill function was considered too dangerous. //Magnus > -----Original Message----- > From: pgsql-general-owner@postgresql.org > [mailto > Sent: Wednesday, January 12, 2005 7:00 PM > To: pgsql-general@postgresql.org > Subject: [GENERAL] Postgresql 8.0 and Cancel/Kill backend functions > > Does anyone know if such functions have been added to version 8? > I saw lots of discussion while searching google and saw > references to patches applied and docs. > > Google link: > > http://groups-beta.google.com/group/...ses.postgresql. patches/browse_thread/thread/8dc627fdbe4b830d/2b4364d42a95b885?q=Cancel% 2FKill+backend+functions+--+docs&_done=%> 2Fgroups%3Fq%3DCancel%2FKill+backend+functions+--+docs%26qt_s% > 3DSearch+Groups%26&_doneTitle=Back+to+Search&&d#2b 4364d42a95b885 > > ---------------------------(end of > broadcast)--------------------------- > TIP 8: explain analyze is your friend > ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings |
| ||||
| Magnus Hagander wrote: > The cancel function is implemented. See > http://developer.postgresql.org/docs...min.html#FUNCT > IONS-ADMIN-SIGNAL-TABLE. > > Kill function was considered too dangerous. Pity - I would have loved this for my test harnesses. I need to drop and recreate the database between each test and, unless I can kill them, a test that fails to close a connection victimizes all subsequent tests. (But not a showstopper in our case - we replace the connect method with a wrapper and have the harnesses keep track of the connection. This only leaves connections opened by spawned processes a problem.) It would be great if this was available as an external method I could install into a particular database. Hmm... I guess it wouldn't be difficult to write this - it would simply involve selecting the procpid from pg_stat_activity and sending a kill signal to it, wouldn't it? -- Stuart Bishop <stuart@stuartbishop.net> http://www.stuartbishop.net/ ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org |