Re: autovacuum ignore tables - Mailing list pgsql-admin

From Sriram Dandapani
Subject Re: autovacuum ignore tables
Date
Msg-id 6992E470F12A444BB787B5C937B9D4DF060E5C05@ca-mail1.cis.local
Whole thread Raw
In response to autovacuum ignore tables  ("Sriram Dandapani" <sdandapani@counterpane.com>)
Responses Re: autovacuum ignore tables  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@sss.pgh.pa.us]
Sent: Friday, September 29, 2006 11:10 AM
To: Sriram Dandapani
Cc: Matthew T. O'Connor; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] autovacuum ignore tables

"Sriram Dandapani" <sdandapani@counterpane.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:

Previous
From: Tom Lane
Date:
Subject: Re: autovacuum ignore tables
Next
From: "Sriram Dandapani"
Date:
Subject: Re: [JDBC] number of transactions doubling