I'll try to do that later. This is on my EDB install on server with no dev tools.
As I recall I think my mingw64 exhibits same issue so I'll do a gdb against both my edb and mingw using the mingw gdb. Can't get to that until later unfortunately. Thanks, Regina -----Original Message----- From: Andres Freund [mailto:and...@2ndquadrant.com] Sent: Monday, December 17, 2012 10:11 AM To: Paragon Corporation 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 10:06:53 -0500, Paragon Corporation wrote: > 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. Unfortunately that doesn't tell us very much. Could you get a backtrace for that? I don't really see which table should receive such large tuples... # SELECT pg_backend_pid(); > 3493 $ gdb -p 3493 (gdb) b hio.c:24 (gdb) c .... # ALTER EXTENSION postgis UPDATE TO "2.1.0SVN"; (gdb) bt full 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
