Andres,
Sorry not sure why I didn't think of that.
The more descriptive error it gives in logs is:
2012-12-17 09:15:10 EST LOG: statement:
SET log_error_verbosity = 'verbose';
2012-12-17 09:15:13 EST LOG: 00000: statement: ALTER EXTENSION postgis
UPDATE TO "2.1.0SVN";
2012-12-17 09:15:13 EST LOCATION: exec_simple_query,
src\backend\tcop\postgres.c:888
2012-12-17 09:15:15 EST ERROR: 54000: row is too big: size 9272, maximum
size 8160
2012-12-17 09:15:15 EST LOCATION: RelationGetBufferForTuple,
src\backend\access\heap\hio.c:241
This is running 9.2.2 64-bit on windows 2008.
I'll look at that section to see what it could be tripping it up. But if
anyone has any ideas if this is a real bug or a "Regina is doing something
stupid" problem, that would be helpful too.
Thanks,
Regina
-----Original Message-----
From: Andres Freund [mailto:and...@2ndquadrant.com]
Sent: Monday, December 17, 2012 9:05 AM
To: l...@pcorp.us
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #7756: When upgrading postgis extension get row is
too big: size 9272, maximum size 8160
Hi,
On 2012-12-17 13:56:13 +0000, l...@pcorp.us wrote:
> row is too big: size 9280, maximum size 8160
If you enable more verbose error output I think you should get a bit more
context, including the table name on which this happens, that might already
help quite a bit. Or do you have that already?
SET log_error_verbosity = 'verbose';
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
