| From: | Chris <dmagick(at)gmail(dot)com> |
|---|---|
| To: | "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Postgres gets stuck |
| Date: | 2006-05-10 00:51:41 |
| Message-ID: | 4461391D.2000800@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> This is a deadly bug, because our web site goes dead when this happens,
> and it requires an administrator to log in and kill the stuck postgres
> process then restart Postgres. We've installed failover system so that
> the web site is diverted to a backup server, but since this has happened
> twice in one week, we're worried.
>
> Any ideas?
Sounds like a deadlock issue.
Do you have query logging turned on?
Also, edit your postgresql.conf file and add (or uncomment):
stats_command_string = true
and restart postgresql.
then you'll be able to:
select * from pg_stat_activity;
to see what queries postgres is running and that might give you some clues.
--
Postgresql & php tutorials
http://www.designmagick.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-05-10 00:59:55 | Re: [PERFORM] Arguments Pro/Contra Software Raid |
| Previous Message | Craig A. James | 2006-05-10 00:38:17 | Postgres gets stuck |