| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Paragon Corporation <lr(at)pcorp(dot)us> |
| Cc: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 18:20:47 |
| Message-ID: | 20121217182047.GB16554@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2012-12-17 12:40:30 -0500, Paragon Corporation wrote:
> I couldn't get my EDB install to give anything meaningful to back trace, but
> same issue happens on my mingw dev install (which is running 9.2.1)
> I have the backtrace for that on this ticket:
>
> http://trac.osgeo.org/postgis/ticket/1959
Its irritating that the error is happening in that simple_heap_update
where the backtrace indicates the old tuple has a t_len = 7011 and the
only variable length field changed is extversion which shouldn't be that
long.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2012-12-17 20:27:06 | Re: Bug with temporary child of a permanent table after recovery |
| Previous Message | Tom Lane | 2012-12-17 17:58:28 | Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160 |