Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: How to track down locks held by recovery process on a slave?
From: reiner peterke <zedaardv@drizzle.com>
In-Reply-To: 
 <CA+vGRtg+8wNugVByhLrhZX=SBnb7k9b9zZfOMPNo7nAEoRAu6w@mail.gmail.com>
Date: Sat, 5 Oct 2013 09:08:37 +0200
Cc: pgsql-admin@postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FBEFAD41-BFC2-463F-8836-074DB85E1E6A@drizzle.com>
References: 
 <CA+vGRtg+8wNugVByhLrhZX=SBnb7k9b9zZfOMPNo7nAEoRAu6w@mail.gmail.com>
To: Amador Alvarez <apradopg@gmail.com>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

First thought is make sure you are looking in the right database.

pg_locks shows data over the entire server, not just the connected database.
pg_class exists for each database  so if you are connected to 'my_database'=
 but the object is in 'your_database', it won't show up in pg_class on 'my_=
database'.

check the database value in pg_locks to verify where you should be looking =
for the object.

reiner

On 5 okt 2013, at 00:48, Amador Alvarez <apradopg@gmail.com> wrote:

> Hi there,
>=20
> I am using a postgres 9.2 slave for some reports and I noticed that somet=
imes they are held up because certain activity on the master like vacuums c=
an affect long queries on a slave .
>=20
> Looking at pg_locks view , I can see that the recovering process on the s=
lave is holding some AccessExclusiveLock locks on relations which numbers t=
hat do not mach any pg_class.oid.=20
>=20
> Any idea How could I find out which relations are locked by the recoverin=
g process?
>=20
>=20
> Thanks in advance,
> A.A.


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin