This doesn’t seem to fix the problem. How do I print out the stack trace in the 
driver?

From: Even Rouault <even.roua...@spatialys.com>
Date: Wednesday, November 29, 2023 at 5:54 AM
Hi,

The logs didn't directly answer my question as they lacked the chain of calls, 
but I believe I figured out the reason. Please try 
https://github.com/OSGeo/gdal/pull/8865<https://urldefense.com/v3/__https:/github.com/OSGeo/gdal/pull/8865__;!!ACWV5N9M2RV99hQ!MF9SjOfGKBc2ARm4bfNzMX-sGw7CXys2OohWuuKXhMG31EkrQNqZkn6xm2MnoCqt3grzKRb9rPrV6jn-lmQqxHx1bEOa$>

Even
Le 29/11/2023 à 02:56, Fengting Chen a écrit :
The attached are two output logs with debug on. You can see that the output 
from GDAL 3.7 has two extra queries at the beginning. These queries only happen 
when the eAccess is GA_ReadOnly. The logs are generated with the same command 
parameters to gdal_translate.

From: Even Rouault 
<even.roua...@spatialys.com><mailto:even.roua...@spatialys.com>
Date: Tuesday, November 28, 2023 at 6:36 PM
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<mailto:gdal-dev@lists.osgeo.org>

https://lists.osgeo.org/mailman/listinfo/gdal-dev<https://urldefense.com/v3/__https:/lists.osgeo.org/mailman/listinfo/gdal-dev__;!!ACWV5N9M2RV99hQ!IqVgHqcg5DBb3fu5ZpXizGqYnezdKvCzFALf06Gt-Vs7RiPPCXFACcefd_slweWtNCqHy-G-OsmoPt9XZqR4DOWs5UiD$>

--

http://www.spatialys.com<https://urldefense.com/v3/__http:/www.spatialys.com__;!!ACWV5N9M2RV99hQ!IqVgHqcg5DBb3fu5ZpXizGqYnezdKvCzFALf06Gt-Vs7RiPPCXFACcefd_slweWtNCqHy-G-OsmoPt9XZqR4DFVEpZ99$>

My software is free, but my time generally not.

--

http://www.spatialys.com<https://urldefense.com/v3/__http:/www.spatialys.com__;!!ACWV5N9M2RV99hQ!MF9SjOfGKBc2ARm4bfNzMX-sGw7CXys2OohWuuKXhMG31EkrQNqZkn6xm2MnoCqt3grzKRb9rPrV6jn-lmQqxN5wEZnr$>

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

Reply via email to