PostgreSQL version: 8.2.4
Exact message: 2011-07-08 09:50:29 ERROR: row is too big: size
103400, maximum size 8136
CREATE TABLE Insurance_cards
card_no bigint NOT NULL,
card_dupl_no smallint NOT NULL,
card_type character varying(1) NOT NULL,
cancel_reason character varying(1) NOT NULL,
cancel_date date NOT NULL,
CONSTRAINT pk_Insurance_cards PRIMARY KEY (card_no , card_dupl_no)
ALTER TABLE uniew_karty_ub OWNER TO "SYSADM";
The problem is repeatable and consistant within this singular database.
2011/7/8 Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>:
> Lukasz Brodziak <lukasz(dot)brodziak(at)gmail(dot)com> wrote:
>> I have a problem during CLUSTER procedure. At some point I get row
>> is too big: size 103400, maximum size 8136 error. How can I
>> determine which row is too big?
> What version of PostgreSQL? What does the table definition look
> like? Did anything unusual happen on this server or to this
> database? Is the problem repeatable and consistent?
> A copy/paste of the exact error message(s) would be better. Be sure
> to check the PostgreSQL log for any clues beyond what you see in the
"Do you bury me when I'm gone
Do you teach me while I'm here
Just as soon I belong
Then it's time I disappear"
In response to
pgsql-admin by date
|Next:||From: Achilleas Mantzios||Date: 2011-07-11 09:15:30|
|Subject: LDAP Authentication : How to set secondary server?|
|Previous:||From: Gavin Flower||Date: 2011-07-10 22:48:03|
|Subject: Re: [SQL] using explain output within pgsql|