Marlowe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 21, 2007 6:05 PM
To: Sachchida Ojha
Cc: Michael Glaesemann; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Autovacuum is running forever
On 8/21/07, Sachchida Ojha <[EMAIL PROTECTED]> wrote:
> Is there any data corruption/dama
I am having some dead locking problem with my app system. Our dev are
debugging the app to find out the cause of the problem. In the mean time
I looked at postgresql.conf file. I found that there is a parameter in
postgresql.conf file deadlock_timeout which was set 1000 (ms). Normally
I see deadlo
I am having some dead locking problem with my app system. Our dev are
debugging the app to find out the cause of the problem. In the mean time
I looked at postgresql.conf file. I found that there is a parameter in
postgresql.conf file deadlock_timeout which was set 1000 (ms). Normally
I see deadlo
quot;;"select * from
pg_stat_activity;";f;"2007-08-22 20:48:25.062663+00";"2007-08-22
20:30:58.600489+00";"10.0.200.165";4170
Regards
Sachchida
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sachc
I see some long running transaction in my pg_activity_log table. My app
becomes almost unusable. My question is
How can I query the database to see what sql these transactions are
running.
16385;"em_db";20893;16386;"em_user";" in
transaction";f;"2007-08-22 20:38:06.527792+00";"2007-08-22
20:37:
esday, August 21, 2007 6:05 PM
To: Sachchida Ojha
Cc: Michael Glaesemann; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Autovacuum is running forever
On 8/21/07, Sachchida Ojha <[EMAIL PROTECTED]> wrote:
> Is there any data corruption/damage to the database if we forcefully
> kill
Is there any data corruption/damage to the database if we forcefully
kill autovacuum using cron job (if it is running longer than a
predefined time frame).
Regards
Sachchida
-Original Message-
From: Sachchida Ojha
Sent: Tuesday, August 21, 2007 5:46 PM
To: 'Michael Glaeseman
operations going on to those assets at the same time.
On server
Cpu util ranging from 10-75%
Mem util ranging from 15-50%
Regards
Sachchida
-Original Message-
From: Michael Glaesemann [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 21, 2007 5:36 PM
To: Sachchida Ojha
Cc: pgsql
: Tuesday, August 21, 2007 5:36 PM
To: Sachchida Ojha
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Autovacuum is running forever
On Aug 21, 2007, at 16:26 , Sachchida Ojha wrote:
> In my OLTP system, we are inserting, updating and deleting the data
> every second.
>
>
Is there any way to stop the autovacuum if it is running longer than 10
min or so?
Is it good idea to kill autovacuum if it is running longer than
expected?
In my OLTP system, we are inserting, updating and deleting the data
every second.
Autovacuum started and never finished slowi
Is there any way to stop the autovacuum if it is running longer than 10
min or so?
Is it good idea to kill autovacuum if it is running longer than
expected?
In my OLTP system, we are inserting, updating and deleting the data
every second.
Autovacuum started and never finished slowi
sender.
-Original Message-
From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 31, 2007 11:28 AM
To: Sachchida Ojha
Cc: Andreas Tille; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] deadlock detected when calling function
(Callfunction_name)
Sachchida Ojha wrote
Hello,
I am getting following error from my application. Can any body tell me
how to find the process name and transaction details when the deadlock
occurred?
This problem did not occur consistently.
Error log
2007-07-30 19:09:12,140 ERROR [se.em.asset.persistence.AssetUpdate]
SQLException ca
Hi,
I am new to PostgreSQL database. Can anybody help me (or point me the
related post) to install PostgreSQL on windows XP from command line.
(From .bat file)
Thanks
Sachi
14 matches
Mail list logo