[postgis-tickets] [PostGIS] #1959: Upgrading with extensions getting a row is too big

[PostGIS]

#1959: Upgrading with extensions getting a row is too big
-----------------------------------+----------------------------------------
 Reporter:  robe                   |       Owner:  robe         
     Type:  defect                 |      Status:  new          
 Priority:  blocker                |   Milestone:  PostGIS 2.0.3
Component:  build/upgrade/install  |     Version:  trunk        
 Keywords:                         |  
-----------------------------------+----------------------------------------
Changes (by robe):

  * milestone:  PostGIS 2.1.0 => PostGIS 2.0.3


Comment:

 Okay going to consider this fixed at r10852 for postgis 2.1.0.
 I still need to make the same change for postgis 2.0 branch.

 I was able to make a fake_postgis extension with nothing but the suspect
 pieces.
 They are discussing the issue here: http://archives.postgresql.org/pgsql-
 bugs/2012-12/msg00166.php

 The fatal mistake I made is that I thought the

 spatial_ref_sys WHERE condition I put in:

 {{{
 SELECT pg_catalog.pg_extension_config_dump('spatial_ref_sys',  'WHERE NOT
 (srid BETWEEN ..')
 }}}

 Needed to prevent spatial_ref_sys records we package from being backed up
 and thus failing on reinstall,  would overwrite the original
 spatial_ref_sys config_dump entry.  Instead it just adds to it and after 3
 upgrades (the array  exceeds the limit of pg_extension space since
 pg_extension doesn't have a companion TOAST table to hold the extra load).

 I'll upgrade my production system running 2.1.0SVN and if that looks good
 I'll backport to 2.0.3 and test by upgrading one of my 2.0 installs.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1959#comment:8>
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.