I will try this way. To turn of SI creation : *SPATIAL_INDEX*=NONE Le lun. 23 mai 2022 à 15:15, Jan Heckman <jan.heck...@gmail.com> a écrit :
> Perhaps the spatial index update (in de DB) slows the insertion. > It might be more efficient to not create the SI in the first run, > then insert more rows and create the SI after all is done. > I don't know how to turn off SI creation in the command line. > > On Mon, May 23, 2022 at 3:04 PM Alexandre Gacon <alexandre.ga...@gmail.com> > wrote: > >> Hello, >> >> I am using ogr2ogr to upload data from several geopackages to a postgis >> database. Some tables contain thousands of rows (buildings for example). >> >> The import of the first file is quite fast (tables are created for the >> first file so PG_USE_COPY is used) but the following file is much slower >> (using INSERT instead of COPY). >> >> How could I data insertion for the other files? Force PG_USE_COPY ? >> Increase the value of GT ? Postpone spatial index creation ? >> >> Should I concatenate all the geopackages first and then insert the data >> in Postgis? >> >> Thank you for your help >> >> -- >> Alexandre Gacon >> _______________________________________________ >> gdal-dev mailing list >> gdal-dev@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/gdal-dev >> > -- Alexandre Gacon
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
