public inbox for [email protected]
help / color / mirror / Atom feedFrom: Marc G. Fournier <[email protected]>
To: Dave Page <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Cannot submit event
Date: Wed, 21 Apr 2004 06:29:22 -0300 (ADT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
On Wed, 21 Apr 2004, Dave Page wrote:
>
>
> > -----Original Message-----
> > From: Josh Berkus [mailto:[email protected]]
> > Sent: 20 April 2004 17:48
> > To: [email protected]
> > Subject: [pgsql-www] Cannot submit event
> >
> > Guys,
> >
> > I've been trying to submit an event for the last 1/2 hour,
> > and it keeps timing
> > out. What's up here?
>
> Dunno, I'm just fixing the bug that Bruce found in the events archive
> and the database is insufferably slow. Any ideas Marc?
Beyond the fact that there is an atrocious amount of connections opened
up:
neptune# ps aux | grep 186_ | awk '{print $12}' | sort | uniq -c
1 186_
3 186_bric
27 186_gborg
104 186_pgsql
nadda ... loadavg is <1 on the database server, and I have pg_autovacuum
enabled to keep tables 'clean' ... does anyone know of a way of having
pg_autovacuum log the database its doing the vacuum on, instead of just
schema.table ... I'm seeing an awful lot of vacuum's of pg_statistic, but
have no idea which database:
[2004-04-21 12:32:29 AM] Performing: VACUUM ANALYZE "public"."siteusers"
[2004-04-21 12:34:09 AM] Performing: VACUUM ANALYZE "pg_catalog"."pg_statistic"
[2004-04-21 12:34:11 AM] Performing: VACUUM ANALYZE "pg_catalog"."pg_statistic"
[2004-04-21 12:34:13 AM] Performing: VACUUM ANALYZE "pg_catalog"."pg_statistic"
[2004-04-21 12:34:15 AM] Performing: VACUUM ANALYZE "pg_catalog"."pg_statistic"
[2004-04-21 08:48:20 AM] Performing: VACUUM ANALYZE "public"."siteusers"
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [email protected] Yahoo!: yscrappy ICQ: 7615664
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Cannot submit event
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox