Re: PG connections going to 'waiting'
От | Alan McKay |
---|---|
Тема | Re: PG connections going to 'waiting' |
Дата | |
Msg-id | 844129e80909051008n138dd2bfv27f13678e38b25fb@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: PG connections going to 'waiting' (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: PG connections going to 'waiting'
Re: PG connections going to 'waiting' |
Список | 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 по дате отправления: