Opened 3 months ago

Closed 6 weeks ago

#5720 closed defect (fixed)

shp2pgsql no longer renaming system column names xmin, xmax

Reported by: turntwo463 Owned by: robe
Priority: high Milestone: PostGIS 3.4.3
Component: utils/shp2pgsql Version: 3.4.x
Keywords: xmin, xmax Cc:

Description

I have previously been using postgis-bundle-pg15-3.3.3x64. After upgrading to postgis-bundle-pg16-3.4.1x64 (for Windows) some shapefiles no longer load into PostgreSQL.

Here is the output when trying to load one such table:

Field xmin is an FTDouble with width 19 and precision 11 Field xmax is an FTDouble with width 19 and precision 11 Field id is an FTDouble with width 19 and precision 11 Shapefile type: Point Postgis type: POINT[2] SET SET BEGIN ERROR: column name "xmin" conflicts with a system column name ERROR: current transaction is aborted, commands ignored until end of transaction block ERROR: current transaction is aborted, commands ignored until end of transaction block ERROR: current transaction is aborted, commands ignored until end of transaction block invalid command \. ERROR: syntax error at or near "2144173.71033000015" LINE 1: 2144173.71033000015 2144173.71033000015 5571.00000000000 010…

ROLLBACK

Attachments (1)

small_example.7z (1.3 KB ) - added by turntwo463 3 months ago.
Zip of sample shapefile to exhibit issue

Download all attachments as: .zip

Change History (4)

by turntwo463, 3 months ago

Attachment: small_example.7z added

Zip of sample shapefile to exhibit issue

comment:1 by Paul Ramsey <pramsey@…>, 6 weeks ago

In 471644a/git:

Actually retain mangled special column names, references #5720

comment:2 by Paul Ramsey <pramsey@…>, 6 weeks ago

In 5c5a557/git:

Actually retain mangled special column names, references #5720

comment:3 by pramsey, 6 weeks ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.