[postgis-tickets] [PostGIS] #5301: PostgreSQL 11 3.0.1 upgrade to 3.3.2 fails with ERROR: row is too big: size 8824, maximum size 8160

PostGIS trac at osgeo.org
Fri Dec 23 20:08:03 PST 2022


#5301: PostgreSQL 11 3.0.1 upgrade to 3.3.2 fails with ERROR:  row is too big:
size 8824, maximum size 8160
------------------------------------+--------------------------------
  Reporter:  robe                   |      Owner:  strk
      Type:  defect                 |     Status:  closed
  Priority:  medium                 |  Milestone:  PostGIS PostgreSQL
 Component:  build/upgrade/install  |    Version:  3.3.x
Resolution:  fixed                  |   Keywords:
------------------------------------+--------------------------------
Changes (by robe):

 * status:  new => closed
 * resolution:   => fixed
 * milestone:  PostGIS 3.3.3 => PostGIS PostgreSQL

Comment:

 This is fixed.  The issue was the pg_extension table.  I think it was left
 over from a time when PostgreSQL was just appending instead of overwriting
 the configurations


 {{{
 SELECT extcondition, extconfig
         FROM pg_catalog.pg_extension where extname = 'postgis';
 }}}

 Yielded the below


 {{{
 extconfig = 3383360,3383360,3383360
 extcondition = ARRAY[ of 3 text values]
 }}}

 I noticed on my fresh system the arrays had only one element, though the
 extconfig value in it was different, so that changes by system.

 To fix I did:


 {{{
 UPDATE pg_extension SET extcondition =  ARRAY[''], extconfig =
 ARRAY[3383360]  WHERE extname = 'postgis';
 SELECT postgis_extensions_upgrade();
 }}}


 I don't think there is a fix on our end for this kind of issue, and no one
 may ever run into it again. So flipping this to PostgreSQL
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5301#comment:7>
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-tickets mailing list