PostGIS dump/restore fails with duplicate key in spatial_ref_sys

[strk]

Dumping and restoring a database after CREATE EXTENSION POSTGIS fails with this:

pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 3174; 0 51657944 TABLE DATA spatial_ref_sys strk
pg_restore: [archiver (db)] COPY failed for table "spatial_ref_sys": ERROR:  duplicate key value violates unique constraint "spatial_ref_sys_pkey"
DETAIL:  Key (srid)=(7041) already exists.
CONTEXT:  COPY spatial_ref_sys, line 1

[strk]

Same happens with trunk (2.3.0dev). 2.1.9dev is fine. Robe, I guess this is for you ? (or for Paul, as it might be due to spatial_ref_sys update)

[strk]

This was definitely introduced by updating spatial_ref_sys as it doesn't happen before r14598 (see #3427)

[strk]

(In [14619]) Automatically generate system_ref_sys config dump for extension

See #3443

[strk]

(In [14620]) Automatically generate system_ref_sys config dump for extension

Fixes #3443

[strk]

NOTE: I'm not sure 2.2.2dev was affected as I realized I was always using trunk instead. Anyway the automation should be good in any case.

[strk]

Reopening as I just realized the automatically created spatial_ref_sys_dump was created empty by the commits.

[strk]

(In [14649]) Really generate system_ref_sys config dump for extension

See #3443

[strk]

(In [14650]) Really generate system_ref_sys config dump for extension

Closes #3443