Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Paragon Corporation" <lr(at)pcorp(dot)us>
Cc: "'Andres Freund'" <andres(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160
Date: 2012-12-17 17:58:28
Message-ID: 27985.1355767108@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Paragon Corporation" <lr(at)pcorp(dot)us> writes:
> The postgis extension has a big custom WHERE condition used to exclude the
> range of spatial_ref_sys records we package postgis from being backed up.

> pg_extension seems to hold that value in the extcondition column and for
> each upgrade I do adds another array entry. Though that might be by design
> to keep track of previous versions and maybe the designers weren't expecting
> someone crazy enough to stuff in a largish where condition :)

For those of us who don't have the latest postgis and all its
dependencies installed, could you extract just the steps of the install
and upgrade scripts that reference this configuration table?

I can see how we might get to this if you were dropping and re-adding
the config table in each cycle, but perhaps that's not what you're doing.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2012-12-17 18:20:47 Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160
Previous Message Paragon Corporation 2012-12-17 17:40:30 Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160