FYI - this have been patched in the latest Postgresql drivers. I worked
around this problem so we dont need to upgrade right away. Maybe
upgrade the PostgreSQL JDBC driver next time there's an offical
postgresql JDBC release?
[EMAIL PROTECTED] wrote:
I've applied a patch for this to 8.0,
David Blasby wrote:
Okay, I've found a pretty nasty bug in the PostGIS driver.
My dataset is a table with about 250 rows in it. Each row has the
VMAP0 dataset polygon of a country in. Each row is large.
If you look closely at the JDBC datastore, you'll notice that it will
fetch 200 rows at
David Blasby wrote:
Okay, I've found a pretty nasty bug in the PostGIS driver.
My dataset is a table with about 250 rows in it. Each row has the VMAP0
dataset polygon of a country in. Each row is large.
If you look closely at the JDBC datastore, you'll notice that it will
fetch 200 rows
Most of the connection pooling is actually done by the Postgresql JDBC
driver, but there's a proxy object on top of it thats hard to look inside.
I talked to the Postgresql JDBC mailing list and they said oops - it
should reset the stream so its in a consistent state. Dont know when
this
Okay, I've found a pretty nasty bug in the PostGIS driver.
My dataset is a table with about 250 rows in it. Each row has the VMAP0
dataset polygon of a country in. Each row is large.
If you look closely at the JDBC datastore, you'll notice that it will
fetch 200 rows at a time - which means
