Hi, If you work with a Postgres database, why don't you do this directly in the database? It seems odd to use ogrinfo to do such updates in database.
Regards Alexandre Le jeu. 9 juin 2022 à 08:50, Andreas Oxenstierna < [email protected]> a écrit : > Dear developers > > Ogr SQL update capabilities are really impressing but there is one major > performance issue with update of many features, exemplified by: > ogrinfo -dialect sqlite -sql "UPDATE <table> SET x = 1" PG:”<connection>" > > This is painfully slow because ogr updates features one by one and > furthermore updates all existing attributes incl. geometries. > Eg. updating 10000 features in pgAdmin/psql with UPDATE <table> SET x = 1 > executes in milliseconds but takes several minutes with ogr. > > The current ogr functionality is also not correct from a database > transactional point of view. > > I found an old RFC, > https://gdal.org/development/rfc/rfc13_createfeatures.html, requesting > this but it was withdrawn for reasons not anymore digitally available. > > Best Regards > > Andreas Oxenstierna > T-Kartor Geospatial AB > Olof Mohlins väg 12 Kristianstad > mobile: +46 733 206831 > mailto: [email protected] > www.t-kartor.com > _______________________________________________ > gdal-dev mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/gdal-dev > -- Alexandre Gacon
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
