Ropel, thank you. I'm looking for a better solution because
1. Some deletes take big amount of time. This increases run time a LOT 2. This requires the use of transaction if somebody changes data between SELECT COUNT(*) and DELETE commands. When transaction isolation level I must set for this ? Can I use default isolation level? Andrus. > At least, you can do a "select count(*) from ..." just before the delete, > better if inside a transaction, if the query itself is not too much > expensive > >>I ran DELETE command from my ODBC client application. >>I want to get the number of rows deleted by this DELETE command. >> >>I read the DELETE command docs but havent found any function. >> >>Any idea ? >> >>Andrus. >> >> >>---------------------------(end of broadcast)--------------------------- >>TIP 3: Have you checked our extensive FAQ? >> >> http://www.postgresql.org/docs/faq >> >> >> > > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
