Werner vd Merwe wrote:

Output of VACUUM ANALYSE VERBOSE pg_listener:

Query OK, 0 rows affected (0.06 sec)
INFO:  vacuuming "pg_catalog.pg_listener"
INFO:  "pg_listener": found 0 removable, 0 nonremovable row versions in 0
pages
INFO:  analyzing "pg_catalog.pg_listener"
INFO:  "pg_listener": 0 pages, 0 rows sampled, 0 estimated total rows



No problems there.

At any given time we have between 10 and 20 IDLE connections.



How long have the transactions been IDLE for? Do the IDLE transactions have any locks on anything (check pg_locks)?

I suspect that (gently) killing the IDLE transactions that are sitting around doing nothing will prevent you from having to restart the postmaster.

--
Brad Nicholson Database Administrator, Afilias Canada Corp.




-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brad Nicholson
Sent: 14 March 2005 07:10 PM
To: PgSQL Admin
Subject: Re: [ADMIN] Performance Question

I'm wondering if long running transacations might be the cause (you'll likely want to do this while perfomance is suffering).

Have a look at pg_stat_activity and see if there are any long running transacations (or any idle transactions).

I'd also be curious to see the output  of the following:

VACUUM ANALYZE VERBOSE pg_listener;






---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Reply via email to