| | 436 | === OGR_PG_CURSOR_PAGE === |
| | 437 | |
| | 438 | PostgreSQL driver specific. Set the number of rows retrieved for each cursor fetch. |
| | 439 | |
| | 440 | === PG_USE_COPY === |
| | 441 | |
| | 442 | This may be "YES" for using COPY for inserting data to PostgreSQL. COPY is significantly faster than INSERT. Starting with GDAL 2.0, COPY is used by default when inserting from a table that has just been created. |
| | 443 | |
| | 444 | === PG_USE_BASE64 === |
| | 445 | (GDAL >= 1.8.0) If set to "YES", geometries will be fetched as BASE64 encoded EWKB instead of canonical HEX encoded EWKB. This reduces the amount of data to be transferred from 2 N to 1.333 N, where N is the size of EWKB data. However, it might be a bit slower than fetching in canonical form when the client and the server are on the same machine, so the default is NO. |
| | 446 | |
| | 447 | === OGR_TRUNCATE === |
| | 448 | (GDAL >= 1.11) If set to "YES", the content of the table will be first erased with the SQL TRUNCATE command before inserting the first feature. This is an alternative to using the -overwrite flag of ogr2ogr, that avoids views based on the table to be destroyed. Typical use case: "ogr2ogr -append PG:dbname=foo abc.shp --config OGR_TRUNCATE YES". |
| | 449 | |
