[postgis-devel] [PostGIS] #1815: spatial_ref_sys table cannot be dumped using pg_dump when installed as an extension
PostGIS
trac at osgeo.org
Mon May 14 09:28:20 PDT 2012
#1815: spatial_ref_sys table cannot be dumped using pg_dump when installed as an
extension
---------------------+------------------------------------------------------
Reporter: chander | Owner: pramsey
Type: defect | Status: new
Priority: high | Milestone: PostGIS 2.0.1
Component: postgis | Version: 2.0.x
Keywords: |
---------------------+------------------------------------------------------
The current packaging of PostGIS's spatial_ref_sys table means that it's
not dump-able using the pg_dump tool.
This means that a full backup of a database does not include dumps of the
spatial_ref_sys table when made by standard postgresql backup tools.
Furthermore, even specifying the table name exactly doesn't cause it to
get dumped.
Ref this email from Tom Lane re this issue:
http://archives.postgresql.org/pgsql-admin/2012-05/msg00051.php
Seems like this is a high priority issue - anyone backing up a PostGIS 2.0
install using the standard PostgreSQL dump tools will not retain in their
backups any local changes to the spatial_ref_sys table, which may render a
restore unusable for certain types of queries (without adding these back
in.)
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1815>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-devel
mailing list