Hi,
Please share the stack trace (on a debug build) of both instances where
GDALOpen() is called
Even
Le 28/11/2023 à 23:40, Fengting Chen via gdal-dev a écrit :
Hi,
I noticed from the GeoRaster driver that in GDAL 3.6 and 3.7 (maybe
3.8 too), there are two GDALOpen() calls on the driver with
GDALOpenInfo eAccess as GA_ReadOnly, even when the GeoRaster is the
output format in gdal_translate command. There are no such calls in
GDAL 3.4. I am wondering if these invocations of Open() with eAccess
as GA_ReadOnly are necessary when the driver is the output driver.
This has caused performance issue for the GeoRaster driver when a user
is trying to load the data into Oracle database because it has two
unnecessary reads from the database. If these Open() calls are
unavoidable, how to differentiate the calls whether it is as input or
as output in the gdal_translate command?
Thanks.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
