Skip site navigation (1) Skip section navigation (2)

Re: autovacuum ignore tables

From: "Sriram Dandapani" <sdandapani(at)counterpane(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>,<pgsql-admin(at)postgresql(dot)org>
Subject: Re: autovacuum ignore tables
Date: 2006-09-29 18:21:50
Message-ID: 6992E470F12A444BB787B5C937B9D4DF060E5C05@ca-mail1.cis.local (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
I see RowExclusiveLocks for all the jdbc inserts

Real question is: Why do the INSERTS go into wait state as soon as the
lock table statement is issued on the parent?

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us] 
Sent: Friday, September 29, 2006 11:10 AM
To: Sriram Dandapani
Cc: Matthew T. O'Connor; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] autovacuum ignore tables 

"Sriram Dandapani" <sdandapani(at)counterpane(dot)com> writes:
> I tried your code with the lock table followed by drop.
> The lock table goes into a wait state AND all INSERTS (even new ones
> coming in) go into a wait state.

Well, it's waiting for something.  Try looking in pg_locks to see which
transaction is blocking it.

			regards, tom lane


pgsql-admin by date

Next:From: Sriram DandapaniDate: 2006-09-29 18:31:11
Subject: Re: [JDBC] number of transactions doubling
Previous:From: Tom LaneDate: 2006-09-29 18:10:06
Subject: Re: autovacuum ignore tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group