Skip site navigation (1) Skip section navigation (2)

Strange error message with 7.0beta1

From: Kyle Bateman <kyle(at)actarg(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Subject: Strange error message with 7.0beta1
Date: 2000-03-03 20:45:07
Message-ID: 38C02452.128EE6B6@actarg.com (view raw or flat)
Thread:
Lists: pgsql-sql
When trying to load my data from a 6.5 pg_dump, I got the error message:

psql:/tmp/ati-tmp.sql:87: ERROR:  Tuple is too big: size 8164, max size
8140

I trimmed back the dump file to a minimum of these commands that will
still generate the error:

CREATE TABLE "exp_log" (
        "expnum" text,
        "amount" float8,
        "tdate" date,
        "toid" int4,
        "pdto" text,
        "memo" text,
        "status" character varying(2),
        "etype" character varying(1),
        "glid" int4,
        "blink" int4);
CREATE TABLE "whold_log" (
        "expnum" text,
        "gross" float8,
        "fed" float8,
        "ssec" float8,
        "mcare" float8,
        "state" float8,
        "garn" float8,
        "med" float8,
        "dent" float8,
        "w125" float8,
        "w401k" float8,
        "eic" float8,
        "other" float8,
        "othacc" character varying,
        "cost" float8,
        "allow" int4,
        "taxstate" character varying(4));
CREATE TABLE "payroll_log" (
        "expnum" text,
        "amount" float8,
        "tdate" date,
        "empl_id" int4,
        "pdto" text,
        "memo" text,
        "status" character varying(2),
        "glid" int4,
        "gross" float8,
        "fed" float8,
        "ssec" float8,
        "mcare" float8,
        "state" float8,
        "garn" float8,
        "med" float8,
        "dent" float8,
        "w125" float8,
        "w401k" float8,
        "eic" float8,
        "other" float8,
        "othacc" character varying,
        "cost" float8,
        "allow" int4,
        "taxstate" character varying(4));
CREATE RULE "_RETpayroll_log" AS
        ON SELECT TO "payroll_log"
        DO INSTEAD
        SELECT  "e"."expnum",
                "e"."amount",
                "e"."tdate",
                "e"."toid" AS "empl_id",
                "e"."pdto",
                "e"."memo",
                "e"."status",
                "e"."glid",
                "w"."gross",
                "w"."fed",
                "w"."ssec",
                "w"."mcare",
                "w"."state",
                "w"."garn",
                "w"."med",
                "w"."dent",
                "w"."w125",
                "w"."w401k",
                "w"."eic",
                "w"."other",
                "w"."othacc",
                "w"."cost",
                "w"."allow",
                "w"."taxstate"
        FROM "exp_log" "e", "whold_log" "w"
        WHERE ("e"."etype" = 'p'::"varchar")
        AND ("e"."expnum" = "w"."expnum");

As the SQL was generated by a previous copy of PostgreSQL, I figured it
might be a problem with the 7.0beta1.

Any ideas?

Attachment: kyle.vcf
Description: text/x-vcard (291 bytes)

Responses

pgsql-sql by date

Next:From: Kyle BatemanDate: 2000-03-03 21:37:48
Subject: ENUM Type
Previous:From: Kyle BatemanDate: 2000-03-03 18:19:25
Subject: 7.0beta bug (or feature)?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group