On 2009-01-28, Abdul Rahman wrote:
> --0-2110834523-1233119974=:72728
> Content-Type: text/plain; charset=us-ascii
>
> 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 ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Abdul Rahman wrote:
> 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?
>
It could be a ton of things, but as an example, if
Well Jaime,
I executed all the delete queries one by one. Now I am unable to understand
that why it took sufficient time to run the last query before cancellation.
i.e. delete from ci_cif_v where req_id='0824100207';
This morning it performed the delete operation and deleted certain number of
On Wed, Jan 28, 2009 at 2:10 AM, Abdul Rahman wrote:
> Thanks Jaime,
> Plz consider the actual log files to explore the issue in detail. Because I
> have pasted the log files of client machine, I am using (sorry).
>
>
> 2009-01-27 18:29:25 STATEMENT: delete from ci_cin_type_v where
> req_id='0824
: 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
Thanks Jaime,
Plz consider the actual log files to explore the issue in detail. Because I
have pasted the log files of client machine, I am using (sorry).
2009-01-27 18:29:25 STATEMENT: delete from ci_cin_type_v where
req_id='0824100207'
delete from ci_cust_type_v where req_id='0824100207
On Wed, Jan 28, 2009 at 1:29 AM, Abdul Rahman wrote:
> Welcome Jcasanov,
>
> Here is the output of the log files:
>
> 2009-01-27 09:24:18 FATAL: the database system is starting up
> 2009-01-27 09:24:19 LOG: database system was shut down at 2009-01-26
> 18:34:53
> 2009-01-27 09:24:19 LOG: checkp
Welcome Jcasanov,
Here is the output of the log files:
2009-01-27 09:24:18 FATAL: the database system is starting up
2009-01-27 09:24:19 LOG: database system was shut down at 2009-01-26 18:34:53
2009-01-27 09:24:19 LOG: checkpoint record is at 0/1B9F92C8
2009-01-27 09:24:19 LOG: redo record i
On Wed, Jan 28, 2009 at 12:56 AM, Abdul Rahman wrote:
>
> What do the logs show?
>
> Message just showed the time it took to delete certain number of records.
>
can you show that message? copy 'n pasted from logs!!
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
AsesorÃa y d
On Wed, Jan 28, 2009 at 12:19 AM, Abdul Rahman wrote:
> Dear All,
>
> PostgreSQL does not perform rollback action. Is it true?
>
no. postgresql executes all statements that are outside an explicit
transaction in its own implicit one [1] executing commit at the end,
if you cancelled the query the
Thanks Justin,
Answers of your technical
questions are as under:
What does the sql statement look like?
delete from ci_cif_v where
req_id='0824100207';
Where was the statement run?
On SQL pan of pgAdmin-III
How was the statement killed?
By
clicking the Cancel Query button ->
What do the logs show?
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 actio
12 matches
Mail list logo
