Very nice! Most probably it was waiting for something else. This is the reason the query executed today and clearly showed certain number of rows deleted. But what ELSE?
________________________________ From: Sim Zacks <s...@compulab.co.il> To: Abdul Rahman <abr_...@yahoo.com> Sent: Wednesday, January 28, 2009 12:08:28 PM Subject: Re: [GENERAL] Rollback of Query Cancellation -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Its very possible that the reason that the query was because there was a lock on the table. If you run select * from pg_stat_activity while the query is running there is a waiting flag that indicates whether your query is actually being executed or if it is waiting for something else. Sim Abdul Rahman wrote: > Dear All, > > Yesterday I canceled a running query because it was taking long time > (more than 12 minutes) to delete lots of records. Today when I executed > the same query it hardly took few seconds to finish. It clearly explores > that PostgreSQL does not perform rollback action. Is it true? > > Regards, > Abdul Rehman. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmABGwACgkQjDX6szCBa+oOzwCguiRslM90EAKY/wo34htqtXUH hWIAoLkALRcBYEJ7jW5ordKRX73jqyR9 =TqIi -----END PGP SIGNATURE-----
