From: | Abdul Rahman <abr_ora(at)yahoo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Sim Zacks <sim(at)compulab(dot)co(dot)il> |
Subject: | Re: Rollback of Query Cancellation |
Date: | 2009-01-28 07:15:46 |
Message-ID: | 195444.15690.qm@web65706.mail.ac4.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 <sim(at)compulab(dot)co(dot)il>
To: Abdul Rahman <abr_ora(at)yahoo(dot)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-----
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2009-01-28 07:20:41 | Re: Rollback of Query Cancellation |
Previous Message | Abdul Rahman | 2009-01-28 07:10:49 | Re: Rollback of Query Cancellation |