pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Guido Barosio <gbarosio@gmail.com>
To: Scott Barvick <sbarvick@comcast.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum doesn't end
Date: Wed, 3 Aug 2005 14:41:38 +0100
Message-ID: <f7f6b4c705080306414f7fa30e@mail.gmail.com> (raw)
In-Reply-To: <1123075702.3469.14.camel@localhost.localdomain>
References: <1123075702.3469.14.camel@localhost.localdomain>

Usually, on this situations, you've got a deadlock or alike.

What I do is to trace the pid of the vacuum (strace -p pid) and try to guess 
if the vacuum
is working or expecting some semaphore to get green (that would be a problem 
on the db side).

If this is the problem, a quick look into the procs running in the 
pg_Stat_activity table will give
you an idea of the situation. Prolly, nothing was going on when you started 
your vacuum
but somehow, a proc acquired a lock somewhere and the vacuum reached that 
somewhere causing
somekinda wait. 

At least, this is very often in my scenery, using 7.4.3 and linux also.

Regards,
Guido

On 8/3/05, Scott Barvick <sbarvick@comcast.net> wrote:
> 
> 
> I have an application that may add a couple million rows per day so I
> vacuum nightly. The tables never get to more than about 10 million rows
> before I move off the interesting information to other media. Somewhat
> often, my vacuums don't complete as shown from this ps command (usually
> VACUUMs take a couple minutes)
> 
> 4442 ? R 949:07 postgres: postgres tag 127.0.0.1(33420) VACUUM
> 
> and the CPU for postmaster (hyperthreaded linux) will be in the high
> 90s.
> 
> The locks look like:
> scouts=# select * from pg_locks;
> relation | database | transaction | pid | mode |
> granted
> 
> ----------+----------+-------------+-------+--------------------------+---------
> | | 12826125 | 11642 | ExclusiveLock |
> t
> 16839 | 17230 | | 11642 | AccessShareLock |
> t
> 17251 | 17230 | | 4442 | RowExclusiveLock |
> t
> 17251 | 17230 | | 4442 | ShareUpdateExclusiveLock |
> t
> 17246 | 17230 | | 4442 | ShareUpdateExclusiveLock |
> t
> 17246 | 17230 | | 4442 | ShareUpdateExclusiveLock |
> t
> | | 12817402 | 4442 | ExclusiveLock |
> t
> (7 rows)
> 
> 
> I all inserts and maintenance through JDBC and may have inserts going on
> while a different java thread calls the VACUUM command.
> 
> Any thoughts? Can I recover without dropping the server?
> 
> Thanks for any help,
> Scott
> 
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
> 



-- 
"Adopting the position that you are smarter than an automatic
optimization algorithm is generally a good way to achieve less
performance, not more" - Tom Lane.

view thread (3+ messages)  latest in thread

Message-ID: <f7f6b4c705080306414f7fa30e@mail.gmail.com>
Permalink:  ../f7f6b4c705080306414f7fa30e@mail.gmail.com/
Also on:    postgresql.org/message-id/f7f6b4c705080306414f7fa30e@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: gbarosio@gmail.com, sbarvick@comcast.net
  Subject: Re: Vacuum doesn't end
  In-Reply-To: <f7f6b4c705080306414f7fa30e@mail.gmail.com>
  References: <1123075702.3469.14.camel@localhost.localdomain> <f7f6b4c705080306414f7fa30e@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox