[AOLSERVER] PostgreSQL near-lockups

2006-01-16 Thread Dave Siktberg
Janine Sisk recently wrote that she restarts her AOLservers every night to help prevent lockups. I'd like to do that, but often when I do a restart I get several postgresql threads that chew up nearly all the cpu cycles for 30 minutes or more and effectively block access to my site. It appears to

Re: [AOLSERVER] PostgreSQL near-lockups

2006-01-16 Thread Janine Sisk
We have found that some sites, when restarted with "svc -t", go into a funky half-shut-down state and stay there. I don't know why, and it seems to be very consistently some sites (all using PG) and not others. For those sites we use "svc -k", in other words send the kill signal instead o

Re: [AOLSERVER] PostgreSQL near-lockups

2006-01-16 Thread Dave Siktberg
Thanks! I do use "svc -t" when restarting, so I will try -k and observe what happens. I'll also now look more carefully at the logs -- I think there are some clues I haven't yet picked up. Dave From: "Janine Sisk" <[EMAIL PROTECTED]> Sent: Monday, January 16, 2006 9:04 PM > We have found that

Re: [AOLSERVER] PostgreSQL near-lockups

2006-01-17 Thread Don Baccus
On Monday 16 January 2006 08:17 pm, Dave Siktberg wrote: > Thanks! I do use "svc -t" when restarting, so I will try -k and observe > what happens. I'll also now look more carefully at the logs -- I think > there are some clues I haven't yet picked up. Enable PG logging and examine those logs, as

Re: [AOLSERVER] PostgreSQL near-lockups

2006-01-17 Thread Fred Cox
Let's not forget that properly operating software doesn't require a -k, since it won't get a chance to clean up pid files and the like. This should only be a temporary hack while someone determines what's really happening. Fred --- Don Baccus wrote: > On Monday 16 January 2006 08:17 pm, Dave S

Re: [AOLSERVER] PostgreSQL near-lockups

2006-01-17 Thread Tom Jackson
On Tuesday 17 January 2006 15:41, Fred Cox wrote: > Let's not forget that properly operating software > doesn't require a -k, since it won't get a chance to > clean up pid files and the like. > You don't need pid files. All other files will be closed. I doubt there is any reason to use -t, since i

Re: [AOLSERVER] PostgreSQL near-lockups

2006-01-17 Thread Janine Sisk
On Jan 17, 2006, at 5:51 PM, Tom Jackson wrote: If you want a slightly different alternative, try -t, wait a few seconds for most everything to stop, then do a -k, but this behavior has been around for a long time, mostly because people use -t. The thing I don't understand is why this happ

Re: [AOLSERVER] PostgreSQL near-lockups

2006-01-17 Thread Dave Siktberg
- Original Message - From: "Don Baccus" > Enable PG logging and examine those logs, as well. I've taken a break to play with some PG logging on my development machine before doing the same on production -- getting some better instrumentation will be like turning on the light in a dark ro

Re: [AOLSERVER] PostgreSQL near-lockups

2006-01-18 Thread Bas Scheffers
On 18 Jan 2006, at 04:15, Janine Sisk wrote: The thing I don't understand is why this happens to some sites, while others can be restarted with -t all day long and they will never hang. It seems to hint at there being something wrong with the few sites afflicted by this, doesn't it? These s

Re: [AOLSERVER] PostgreSQL near-lockups

2006-01-18 Thread Don Baccus
On Tuesday 17 January 2006 09:05 pm, you wrote: > Am I on the right track with the following? I think so, yes. The #1 question to answer is "are the long-running threads caused by an application query, or something internal to Postgres?" -- Don Baccus Portland, OR http://donb.furfly.net, htt

Re: [AOLSERVER] PostgreSQL near-lockups

2006-01-18 Thread Janine Sisk
On Jan 17, 2006, at 11:40 PM, Bas Scheffers wrote: On 18 Jan 2006, at 04:15, Janine Sisk wrote: The thing I don't understand is why this happens to some sites, while others can be restarted with -t all day long and they will never hang. It seems to hint at there being something wrong with