> On 2025-09-15 19:16 +0200, Ярослав Минин via postgis-users wrote: > > > > Hello! We have stumbled upon a strange issue after upgrading from > > PostGIS 3.3.0 to 3.6.0. > > A simple query like select * from foo.bar where ST_IsValid(geometry) > > executed in DBeaver returns the following error: > > SQL Error [08006]: An I/O error occurred while sending to the backend > > if the size of this table is like 6 Mb or more. While executing > > DBeaver shows something like connection attempts and finally > > invalidates/reconnects with this error message. > > That error message originates from pgJDBC [1]. Do you have to the full stack > trace? Without that info it's impossible for us to track down the cause. > But I > doubt that it has anything to do with PostGIS or even the Postgres backend > judging by the implementation at [1] which may fail when it cannot copy the > InputStream. Better raise that issue with DBeaver or pgJDBC itself. > > Nevertheless, can you reproduce this error with psql to rule out any > interference from DBeaver/JDBC? Perhaps also the server log? > > [1] > https://github.com/pgjdbc/pgjdbc/blob/a3be9d5ec7efe18e88e44f1637c459e > b2bb4cc15/pgjdbc/src/main/java/org/postgresql/util/StreamWrapper.java#L8 > 6 > > -- > Erik Wienhold
If you can also output the info from SELECT version(), postgis_full_version(); That would help. I do recall that there are some issues with lower postgis functions that happen because we replaced them. So if your output has something like "Needs upgrade" You may need to do a SELECT postgis_extensions_upgrade();
