Re: Late night problems

Ahhhh

Sunday night = vacuum full on the database :(

Cron job removed...

Regards,

John

> -----Original Message-----
> From: pgsql-www-owner(at)postgresql(dot)org
> [mailto:pgsql-www-owner(at)postgresql(dot)org] On Behalf Of Greg
> Sabino Mullane
> Sent: Monday, 28 June 2004 8:49 PM
> To: pgsql-www(at)postgresql(dot)org
> Subject: Re: [pgsql-www] Late night problems
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> > I don't see this from .uk. In fact, search.postgresql.org has just
> > recently been moved to new hardware in .au which offers far greater
> > performance - for example, I just searched then entire database for
> > 'referential integrity' and saw the results page, including
> all images
> > and ads in about 3 seconds.
>
> Seems to be better now. Just now, searching for "speed" in
> the archives took "0.060" seconds according to the results
> pae. Last night, it took 108 seconds. Even navigating from
> one message to the next in a thread took about 20 seconds for
> each page to load. This has happened
> before: I'll whip up a cron script to track basic
> responsiveness over time.
>
> - --
> Greg Sabino Mullane greg(at)turnstep(dot)com
> PGP Key: 0x14964AC8 200406280647
>
> -----BEGIN PGP SIGNATURE-----
>
> iD8DBQFA3/gevJuQZxSWSsgRAm2SAJ9r8XBTTl57gwexKNRt6V+C79M6KQCeItos
> thfSOg9fPj4sc9DwPMVA8So=
> =54Ol
> -----END PGP SIGNATURE-----
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index
> scan if your
> joining column's datatypes do not match
>
>