Greg Smith wrote:
On Mon, 3 Nov 2008, Jason Long wrote:
For some reason Postgres is pegging my CPU and I can barely log on to
reboot the machine.
Take a look at pg_stat_activity when this happens to see what's going
on. Also, try running "top -c" to see what is going on (the -c
displays ext
On Mon, 3 Nov 2008, Jason Long wrote:
For some reason Postgres is pegging my CPU and I can barely log on to reboot
the machine.
Take a look at pg_stat_activity when this happens to see what's going on.
Also, try running "top -c" to see what is going on (the -c displays extra
information for
Jason Long wrote:
Scott Marlowe wrote:
On Mon, Nov 3, 2008 at 12:25 PM, Scott Marlowe <[EMAIL PROTECTED]> wrote:
On Mon, Nov 3, 2008 at 11:30 AM, Jason Long
<[EMAIL PROTECTED]> wrote:
I am running PostgreSQL 8.3.4 on Centos 5.2 with a single Xeon 5472, 1600
MHz, 12 MB cache, 3.0 GHz qu
Scott Marlowe wrote:
On Mon, Nov 3, 2008 at 12:25 PM, Scott Marlowe <[EMAIL PROTECTED]> wrote:
On Mon, Nov 3, 2008 at 11:30 AM, Jason Long
<[EMAIL PROTECTED]> wrote:
I am running PostgreSQL 8.3.4 on Centos 5.2 with a single Xeon 5472, 1600
MHz, 12 MB cache, 3.0 GHz quad core, and 4 GB R
On Mon, Nov 3, 2008 at 12:25 PM, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 3, 2008 at 11:30 AM, Jason Long
> <[EMAIL PROTECTED]> wrote:
>> I am running PostgreSQL 8.3.4 on Centos 5.2 with a single Xeon 5472, 1600
>> MHz, 12 MB cache, 3.0 GHz quad core, and 4 GB RAM.
>>
>> My database i
On Mon, Nov 3, 2008 at 11:30 AM, Jason Long
<[EMAIL PROTECTED]> wrote:
> I am running PostgreSQL 8.3.4 on Centos 5.2 with a single Xeon 5472, 1600
> MHz, 12 MB cache, 3.0 GHz quad core, and 4 GB RAM.
>
> My database is only about 50 MB and there are only about 20 users.
>
> For some reason Postgres
Jason Long <[EMAIL PROTECTED]> writes:
> For some reason Postgres is pegging my CPU and I can barely log on to
> reboot the machine.
Well, you need to find out why. Turning on query logging (see
log_statement) would probably be a good first step --- it'd help
you determine if there's a specific
On Monday 03 November 2008, Jason Long <[EMAIL PROTECTED]>
wrote:
> I would greatly appreciate any advice on debugging this problem. While
> there are relatively live few users the data is extremely important and
> the users will not wait for me to see what is wrong. They demand
> immediate reso
