Re: PG connections going to 'waiting' - Mailing list pgsql-general

From Alan McKay
Subject Re: PG connections going to 'waiting'
Date
Msg-id 844129e80909051008n138dd2bfv27f13678e38b25fb@mail.gmail.com
Whole thread Raw
In response to Re: PG connections going to 'waiting'  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PG connections going to 'waiting'  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: PG connections going to 'waiting'  (Joshua Tolley <eggyknap@gmail.com>)
List pgsql-general
> pg_locks?  Somebody taking exclusive lock on a widely-used table might
> explain that.

OK, in theory we could do the following, no?

Use our PITR logs to restore a tertiary system to the point when we
were having the problem (we have a pretty wide 2 or 3 hour window to
hit), then query the pg_locks table on that system?

If so, is it possible to only restore a subset of the DB to that point
- in particular just this table?

The problem is that our DB is pretty massive and this could take an
extremely long time.


--
“Don't eat anything you've ever seen advertised on TV”
         - Michael Pollan, author of "In Defense of Food"

pgsql-general by date:

Previous
From: Alan McKay
Date:
Subject: Re: PG connections going to 'waiting'
Next
From: Tom Lane
Date:
Subject: Re: PG connections going to 'waiting'