Re: BUG #16275: we are facing error aspsycopg2.errors.ProgramLimitExceeded: row is too big: size 24520, maximum - Mailing list pgsql-bugs

From Tomas Vondra
Subject Re: BUG #16275: we are facing error aspsycopg2.errors.ProgramLimitExceeded: row is too big: size 24520, maximum
Date
Msg-id 20200225150534.bsjf3uwemiwwpbzg@development
Whole thread Raw
In response to BUG #16275: we are facing error as psycopg2.errors.ProgramLimitExceeded: row is too big: size 24520, maximum  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Tue, Feb 25, 2020 at 06:49:06AM +0000, PG Bug reporting form wrote:
>The following bug has been logged on the website:
>
>Bug reference:      16275
>Logged by:          prachi surangalikar
>Email address:      prachi.prachi97ps@gmail.com
>PostgreSQL version: 12.0
>Operating system:   windows 10
>Description:
>
>i am trying this program using python, i followed the steps but it did not
>helped; how  can i solve this error please tell us
>

This simply meas that you're trying to insert data into a table, but the
resulting row is far too wide (it needs to fit into 8kB data page, but
it's way larger than that).

What exactly is happening depends on how is the table defined. Maybe it
has too many columns, or maybe the columns are wide enough to overflow
the page. Or something like that.

In general, I doubt this is a bug - it's expected behavior, essentially
an implementation limitation. But it's hard to say unless you show us
the table schema.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-bugs by date:

Previous
From: Alexey Bashtanov
Date:
Subject: planner weirdness: a join uses nestloop with checking condition whenthere are two subplan-or-hashed subqueries
Next
From: PG Bug reporting form
Date:
Subject: BUG #16276: Server crash on an invalid attempt to attach a partition to an index