On Jul 19, 2009, at 11:40 AM, Jeff Johnson wrote:
Two questions come up for me:
1. Why were no such errors in the past with 5.0.x and <= 5.1.[7-9]
(approximately)?
Dunno. DB_RUNRECOVERY is ultimately a data, not an implementation,
issue.
2. What can we do to workaround this problem? Perhaps run
the "rpm -q" operations in a special RPMDB read-only mode or
something like this? Perhaps --define '__dbi_private yes'?
There's lots of ways to workaround (but not DB_PRIVATE disabling
locks).
Are chroot's involved?
What is being queried?
Do you have a definite reproducer or is the problem just occurring
occaisionally randomly?
Without further information, there's nothing I can do.
73 de Jeff
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List [email protected]
