Hunter-
Have you done a vacuum analyze since the data reload? The stats are
different enough that the planner gets all confused if you don't analyze
right away.
Regards,
-Nick
--------------------------------------------------------------------------
Nick Fankhauser nickf@ontko.com Phone 1.765.935.4283 Fax 1.765.962.9788
Ray Ontko & Co. Software Consulting Services http://www.ontko.com/
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Hunter Hillegas
> Sent: Tuesday, June 04, 2002 9:28 PM
> To: PostgreSQL
> Subject: [GENERAL] Postgres 7.2.1 Really Spinning the CPU
>
>
> Just got my new server up and running with PostgreSQL 7.2.1... I
> am running
> Jive Forums against it.
>
> I used pg_dump to extract the data from the old server, and used 'psql
> database < file.sql' to get the data into the new database.
>
> Now I have it up and running and PostgreSQL is using up to 40% of
> the CPU...
> My site is not heavily trafficked, so this seems out of place.
>
> Is it possible that Jive's indexes were not re-created properly? The old
> server was also 7.2.1.
>
> I have bumped up shared memory:
>
> [root@vader init.d]# cat /proc/sys/kernel/shmmax
> 128000000
>
> and in my postgresql.conf I have increased my shared buffers to 3000.
>
> Any ideas how to figure out what is going on?
>
> Thanks,
> Hunter
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
