| From: | Ries van Twisk <pg(at)rvt(dot)dds(dot)nl> |
|---|---|
| To: | "Ridvan Lakas ng Bayan S(dot) Baluyos" <ridvan(at)baluyos(dot)net> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: pg_locks concern |
| Date: | 2009-07-03 02:49:59 |
| Message-ID: | 7FD265C1-1A94-4117-997A-79208F2C41D8@rvt.dds.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
> Hi list,
>
> I'm new in administering postgres database server. I would like to
> ask a question what's causing these locks and what are the
> consequences?
>
> Currently, we have single application that consumes 100% CPU
> Utilization of our server.
>
> Here's the specs of our server,
> HPDL580
> Quad Quad (16 Logical Processors)
> 24GB Memory
> 4TB Storage
>
>
> TIA,
>
> RIdvan
RIdvan,
If you application sit's at 100% then it's not PG and you need to look
there rather then looking into PostgreSQL.
It also helps if you tell is more about the application, what version
of PostgreSQL you have
and what queries are running..
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Wood | 2009-07-03 11:32:57 | Possibly corrupted pg_control file after machine crash |
| Previous Message | Ridvan Lakas ng Bayan S. Baluyos | 2009-07-03 02:31:34 | pg_locks concern |