Обсуждение: Strange error message with 7.0beta1

Поиск
Список
Период
Сортировка

Strange error message with 7.0beta1

От
Kyle Bateman
Дата:
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?

Вложения

Re: [SQL] Strange error message with 7.0beta1

От
Peter Eisentraut
Дата:
Kyle Bateman writes:

> 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

> CREATE TABLE "exp_log" (

> CREATE TABLE "whold_log" (

> CREATE TABLE "payroll_log" (

> CREATE RULE "_RETpayroll_log" AS
>         ON SELECT TO "payroll_log"
>         DO INSTEAD
>         SELECT  "e"."expnum",
[ a lot ]
>         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.

Due to some internal changes the rule descriptor (so to speak) has
expanded in its size so now it doesn't fit within a tuple anymore. There
were some changes done in this area just the other day, so you might want
to get a later beta and try it out. (I think they make these every night.)

-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



Re: [SQL] Strange error message with 7.0beta1

От
Bruce Momjian
Дата:
> 
> Due to some internal changes the rule descriptor (so to speak) has
> expanded in its size so now it doesn't fit within a tuple anymore. There
> were some changes done in this area just the other day, so you might want
> to get a later beta and try it out. (I think they make these every night.)
> 

Get the snapshot, not beta1.

--  Bruce Momjian                        |  http://www.op.net/~candle pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026