On 7 July 2010 21:32, Graham Leggett minf...@sharp.fm wrote:
On 07 Jul 2010, at 4:43 PM, Greg Monroe wrote:
Torque has been using Village pretty much since day 1.. and AFAIK the
Village has been using metadata as long. If you didn't have performance
problems before, it's probably a JDBC
Torque has been using Village pretty much since day 1.. and AFAIK the
Village has been using metadata as long. If you didn't have performance
problems before, it's probably a JDBC version problem.
FWIW, getting rid of Village (or highly modifying it) is a 4.0 goal. But
AFAIK, the Village use
-user@db.apache.org
Sent: Wed, July 7, 2010 11:43:34 AM
Subject: RE: Excessive database queries on postgresql: village metadata queries
Torque has been using Village pretty much since day 1.. and AFAIK the
Village has been using metadata as long. If you didn't have performance
problems before
...
Has anyone encountered this before and managed to work out how to stop
the metadata queries being translated into database queries? I would
expect either the JDBC driver to cache these, or if not for Village to
cache these.
I remember dimly using a patched version of village which
On 07.07.10 19:15, Thomas Fischer wrote:
...
Has anyone encountered this before and managed to work out how to stop
the metadata queries being translated into database queries? I would
expect either the JDBC driver to cache these, or if not for Village to
cache these.
I remember dimly
On 07 Jul 2010, at 4:43 PM, Greg Monroe wrote:
Torque has been using Village pretty much since day 1.. and AFAIK the
Village has been using metadata as long. If you didn't have
performance
problems before, it's probably a JDBC version problem.
I've just methodically tried the postgresql
