Обсуждение: dangling lock information?
I'm currently testing pgAdmin support for slony, on pgsql CVS HEAD, and encounter strange problems from time to time. After dropping and recreating the slony schema, all changes committed and all backends in <IDLE> state, I'm getting "relation with OID xxx does not exist" when I'm trying to add a path. This seems to be triggered inside slony functions when a LOCK _test.pg_config IN EXCLUSIVE MODE is performed. The problem is gone as soon as I close the connection I've been using for prior schema changes, and use a fresh connection. Does this description ring a bell for somebody? Regards, Andreas
On P, 2005-08-28 at 22:23 +0200, Andreas Pflug wrote: > I'm currently testing pgAdmin support for slony, on pgsql CVS HEAD, and > encounter strange problems from time to time. > After dropping and recreating the slony schema, all changes committed > and all backends in <IDLE> state, I'm getting > "relation with OID xxx does not exist" when I'm trying to add a path. > This seems to be triggered inside slony functions when a > LOCK _test.pg_config IN EXCLUSIVE MODE > is performed. > The problem is gone as soon as I close the connection I've been using > for prior schema changes, and use a fresh connection. > > Does this description ring a bell for somebody? seems like the usual "pl/pgsql caches query plans and relation referenced inside the cached plan is gone" thing -- Hannu Krosing <hannu@skype.net>
Hannu Krosing wrote: >On P, 2005-08-28 at 22:23 +0200, Andreas Pflug wrote: > > >>I'm currently testing pgAdmin support for slony, on pgsql CVS HEAD, and >>encounter strange problems from time to time. >>After dropping and recreating the slony schema, all changes committed >>and all backends in <IDLE> state, I'm getting >>"relation with OID xxx does not exist" when I'm trying to add a path. >>This seems to be triggered inside slony functions when a >> LOCK _test.pg_config IN EXCLUSIVE MODE >>is performed. >>The problem is gone as soon as I close the connection I've been using >>for prior schema changes, and use a fresh connection. >> >>Does this description ring a bell for somebody? >> >> > >seems like the usual "pl/pgsql caches query plans and relation >referenced inside the cached plan is gone" thing > > Kind of, but the complete schema including procedures was dropped, so apparently after recreation the old plans were reused?!? Regards, Andreas
On E, 2005-08-29 at 13:09 +0200, Andreas Pflug wrote: > Hannu Krosing wrote: > > >On P, 2005-08-28 at 22:23 +0200, Andreas Pflug wrote: > > > > > >>I'm currently testing pgAdmin support for slony, on pgsql CVS HEAD, and > >>encounter strange problems from time to time. > >>After dropping and recreating the slony schema, all changes committed > >>and all backends in <IDLE> state, I'm getting > >>"relation with OID xxx does not exist" when I'm trying to add a path. > >>This seems to be triggered inside slony functions when a > >> LOCK _test.pg_config IN EXCLUSIVE MODE > >>is performed. > >>The problem is gone as soon as I close the connection I've been using > >>for prior schema changes, and use a fresh connection. > >> > >>Does this description ring a bell for somebody? > >> > >> > > > >seems like the usual "pl/pgsql caches query plans and relation > >referenced inside the cached plan is gone" thing > > > > > Kind of, but the complete schema including procedures was dropped, so > apparently after recreation the old plans were reused?!? In that case this should probably be asked at slony list. Added to CC. -- Hannu Krosing <hannu@skype.net>